Smooth transition between multimedia broadcast multicast service (mbms) and unicast service by demand

ABSTRACT

Techniques are provided for smooth transition between broadcast/multicast transmission and unicast transmission. A method for managing unicast and multicast services switching in a multi-band/multi-frequency wireless communications system (WCS) capable of both unicast and multicast signaling includes determining whether an aggregate demand for a content provided via dedicated unicast transmissions exceeds a threshold. The method includes switching transmission of the content from the dedicated unicast transmissions on one frequency to a multicast transmission on a second or more frequencies in response to determining that the aggregate demand exceeds the threshold.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application for patent claims priority to ProvisionalApplication No. 61/643,128, filed May 4, 2012, entitled “SMOOTHTRANSITION BETWEEN MULTIMEDIA BROADCAST MULTICAST SERVICE AND UNICASTSERVICE BY DEMAND”, Provisional Application No. 61/661,764, filed Jun.19, 2012, entitled “SMOOTH TRANSITION BETWEEN MULTIMEDIA BROADCASTMULTICAST SERVICE (MBMS) AND UNICAST SERVICE BY DEMAND”, and ProvisionalApplication No. 61/801,279, filed Mar. 15, 2013, entitled “SMOOTHTRANSITION BETWEEN MULTIMEDIA BROADCAST MULTICAST SERVICE (MBMS) ANDUNICAST SERVICE BY DEMAND” which are assigned to the assignee hereof,and are hereby expressly incorporated in their entirety by referenceherein.

BACKGROUND

1. Field

Aspects of the present disclosure relate generally to wirelesscommunication systems, and more particularly, to managing demand-basedMultimedia Broadcast Multicast Service in a wireless communicationsnetwork.

2. Background

Wireless communication networks are widely deployed to provide variouscommunication services such as voice, video, packet data, messaging,broadcast (BC), etc. These wireless networks may be multiple-accessnetworks capable of supporting multiple users by sharing the availablenetwork resources. Examples of such multiple-access networks includeCode Division Multiple Access (CDMA) networks, Time Division MultipleAccess (TDMA) networks, Frequency Division Multiple Access (FDMA)networks, Orthogonal FDMA (OFDMA) networks, and Single-Carrier FDMA(SC-FDMA) networks.

A wireless communication network may include a number of base stationsthat can support communication for a number of user equipments (UEs),also referred to as mobile entities. A UE may communicate with a basestation via a downlink and an uplink. The downlink (or forward link)refers to the communication link from the base station to the UE, andthe uplink (or reverse link) refers to the communication link from theUE to the base station. As used herein, a “base station” means an eNodeB(eNB), a Node B, a Home Node B, or similar network component of awireless communications system.

The 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE)represents a major advance in cellular technology as an evolution ofGlobal System for Mobile communications (GSM) and Universal MobileTelecommunications System (UMTS). The LTE physical layer (PHY) providesa highly efficient way to convey both data and control informationbetween base stations, such as evolved Node Bs (eNBs), and mobileentities, such as UEs. In prior applications, a method for facilitatinghigh bandwidth communication for multimedia has been single frequencynetwork (SFN) operation. SFNs utilize radio transmitters, such as, forexample, eNBs, to communicate with subscriber UEs. In unicast (UC)operation, each eNB is controlled so as to transmit signals carryinginformation directed to one or more particular subscriber UEs. Thespecificity of unicast signaling enables person-to-person services suchas, for example, voice calling, text messaging, or video calling.

In broadcast operation, several eNBs in a broadcast area broadcastsignals in a synchronized fashion, carrying information that can bereceived and accessed by any subscriber UE in the broadcast area. Thegenerality of broadcast operation enables greater efficiency intransmitting information of general public interest, for example,event-related multimedia broadcasts. As the demand and system capabilityfor event-related multimedia and other broadcast services has increased,system operators have shown increasing interest in making use ofbroadcast operation in 3GPP networks. In the past, 3GPP LTE technologyhas been primarily used for unicast service, leaving opportunities forimprovements and enhancements related to broadcast signaling.

In LTE, an eMBMS application may provide schedule based eMBMSapplications. In the schedule based eMBMS application, a system operatoron the network side controls transmission of eMBMS content, which occursat a scheduled time. A mobile entity may subscribe to the scheduledtransmission and thereby receive content of interest for the mobileuser. Content offerings available to UEs via eMBMS transmission,however, generally are limited to the operator's scheduled eMBMSofferings. Such scheduled content offerings do not address requests forcontent based on demand such as breaking news, traffic alerts, and moviedownloads, which the UE may receive through a dedicated transmission.Therefore, there is a need for transmission method providing transitionsbetween the dedicated transmission and broadcast transmission of thecontent.

SUMMARY

Methods and apparatus for assigning aggregated component carriers totiming advance groups are described in detail in the detaileddescription, and certain aspects are summarized below. This summary andthe following detailed description should be interpreted ascomplementary parts of an integrated disclosure, which parts may includeredundant subject matter and/or supplemental subject matter. An omissionin either section does not indicate priority or relative importance ofany element described in the integrated application. Differences betweenthe sections may include supplemental disclosures of alternativeembodiments, additional details, or alternative descriptions ofidentical embodiments using different terminology, as should be apparentfrom the respective disclosures.

In an aspect, a method is for managing unicast and multicast servicesswitching in a multi-band/multi-frequency wireless communications system(WCS) capable of both unicast and multicast signaling. The methodincludes determining whether an aggregate demand for a content providedvia dedicated unicast transmissions exceeds a threshold. The methodincludes switching transmission of the content from the dedicatedunicast transmissions on one frequency to a multicast transmission on asecond or more frequencies in response to determining that the aggregatedemand exceeds the threshold.

In another aspect, an apparatus is for managing unicast and multicastservices switching in a multi-band/multi-frequency wirelesscommunications system (WCS) capable of both unicast and multicastsignaling. The apparatus includes at least one processor configured todetermine whether an aggregate demand for a content provided viadedicated unicast transmissions exceeds a threshold, and switchtransmission of the content from the dedicated unicast transmissions onone frequency to a multicast transmission on a second or morefrequencies in response to determining that the aggregate demand exceedsthe threshold. The apparatus includes a memory coupled to the at leastone processor for storing data.

In another aspect, an apparatus is for managing unicast and multicastservices switching in a multi-band/multi-frequency wirelesscommunications system (WCS) capable of both unicast and multicastsignaling. The apparatus includes means for determining whether anaggregate demand for a content provided via dedicated unicasttransmissions exceeds a threshold. The apparatus includes means forswitching transmission of the content from the dedicated unicasttransmissions on one frequency to a multicast transmission on a secondor more frequencies in response to determining that the aggregate demandexceeds the threshold.

In another aspect, computer program product includes a computer-readablemedium storing code for causing at least one computer to: determinewhether an aggregate demand for a content provided via dedicated unicasttransmissions exceeds a threshold; and switch transmission of thecontent from the dedicated unicast transmissions on one frequency to amulticast transmission on a second or more frequencies in response todetermining that the aggregate demand exceeds the threshold.

In another aspect, a method is for managing unicast and multicastservices switching in a wireless mobile entity capable of both unicastand multicast signaling. The method includes receiving a content viamulticast transmission. The method includes determining whether toswitch from receiving the content via the multicast transmission toreceiving the content via dedicated unicast transmission. The methodincludes switching receiving the content via multicast transmission todedicated unicast transmission based in response to determining toswitch.

In another aspect, an apparatus is capable of both unicast and multicastsignaling for managing unicast and multicast services switching. Theapparatus includes at least one processor configured to receive acontent via multicast transmission, determine whether transmission ofthe content received via the multicast transmission is about to end oris no longer available on one or more frequencies, and switch receivingof the content via the multicast transmission to dedicated unicasttransmissions. The apparatus includes a memory coupled to the at leastone processor for storing data.

In another aspect, an apparatus is capable of both unicast and multicastsignaling for managing unicast and multicast services switching. Theapparatus includes means for receiving a content via multicasttransmission. The apparatus includes means for determining whethertransmission of the content received via the multicast transmission isabout to end or is no longer available on one or more frequencies. Theapparatus includes means for switching receiving of the content via themulticast transmission to dedicated unicast transmissions.

In another aspect, computer program product includes a computer-readablemedium storing code for causing at least one computer to: receive acontent via multicast transmission; determine whether transmission ofthe content received via the multicast transmission is about to end oris no longer available on one or more frequencies; and switch receivingof the content via the multicast transmission to dedicated unicasttransmissions.

In another aspect, a method is for managing unicast and multicastservices switching in a wireless mobile entity capable of both unicastand multicast signaling. The method includes receiving a content viadedicated unicast transmission. The method includes determining whetherto switch from receiving the content via the dedicated unicasttransmission to receiving the content via multicast transmission. Themethod includes switching receiving the content via dedicated unicasttransmission to multicast transmission in response to determining toswitch.

In another aspect, an apparatus is capable of both unicast and multicastsignaling for managing unicast and multicast services switching. Theapparatus includes at least one processor configure to receive a contentvia dedicated unicast transmission, determine whether to switch fromreceiving the content via the dedicated unicast transmission toreceiving the content via multicast transmission, and switchingreceiving the content via dedicated unicast transmission to multicasttransmission in response to determining to switch. The apparatusincludes a memory coupled to the at least one processor for storingdata.

In another aspect, an apparatus is capable of both unicast and multicastsignaling for managing unicast and multicast services switching. Theapparatus includes means for receiving a content via dedicated unicasttransmission. The apparatus includes means for determining whether toswitch from receiving the content via the dedicated unicast transmissionto receiving the content via multicast transmission. The apparatusincludes means for switching receiving the content via dedicated unicasttransmission to multicast transmission in response to determining toswitch.

In another aspect, a computer program product includes acomputer-readable medium storing code for causing at least one computerto: receive a content via dedicated unicast transmission; determinewhether to switch from receiving the content via the dedicated unicasttransmission to receiving the content via multicast transmission; andswitch receiving the content via dedicated unicast transmission tomulticast transmission in response to determining to switch.

In another aspect, a method is for managing unicast and multicastservices switching in a wireless communications system (WCS) capable ofboth unicast and multicast signaling. The method includes determiningwhether an aggregate demand for a content provided via dedicated unicasttransmissions exceeds a threshold based on indications received frommobile entities. The method includes switching transmission of thecontent from the dedicated unicast transmissions to a multicasttransmission in response to determining that the aggregate demandexceeds the threshold.

In another aspect, an apparatus is for managing unicast and multicastservices switching in a wireless communications system (WCS) capable ofboth unicast and multicast signaling, the apparatus comprising. Theapparatus includes at least one processor configured to determinewhether an aggregate demand for a content provided via dedicated unicasttransmissions exceeds a threshold based on indications received frommobile entities, and switch transmission of the content from thededicated unicast transmissions to a multicast transmission in responseto determining that the aggregate demand exceeds the threshold. Theapparatus includes a memory coupled to the at least one processor forstoring data.

In another aspect, an apparatus is for managing unicast and multicastservices switching in a wireless communications system (WCS) capable ofboth unicast and multicast signaling. The apparatus includes means fordetermining whether an aggregate demand for a content provided viadedicated unicast transmissions exceeds a threshold based on indicationsreceived from mobile entities. The apparatus includes means forswitching transmission of the content from the dedicated unicasttransmissions to a multicast transmission in response to determiningthat the aggregate demand exceeds the threshold.

In another aspect, a computer program product includes acomputer-readable medium storing code for causing at least one computerto: determine whether an aggregate demand for a content provided viadedicated unicast transmissions exceeds a threshold based on indicationsreceived from mobile entities; and switch transmission of the contentfrom the dedicated unicast transmissions to a multicast transmission inresponse to determining that the aggregate demand exceeds the threshold.

In another aspect, a method is for managing demand-based multicastservices in a wireless communication system (WCS) capable of bothunicast and multicast signaling. The method includes determining whethera content can be delivered via unicast transmission and multicasttransmission. The method includes provisioning the unicast transmissionand multicast transmission in response to determining the content can bedelivered via unicast transmission and multicast transmission. Themethod includes switching between the unicast transmission and themulticast transmission.

In another aspect, an apparatus is for managing demand-based multicastservices in a wireless communication system (WCS) capable of bothunicast and multicast signaling. The apparatus includes at least oneprocessor configured to (a) determine whether a content can be deliveredvia unicast transmission and multicast transmission, (b) provision theunicast transmission and multicast transmission in response todetermining the content can be delivered via unicast transmission andmulticast transmission, and (c) switch between the unicast transmissionand the multicast transmission. The apparatus includes a memory coupledto the at least one processor for storing data.

In another aspect, an apparatus is for managing demand-based multicastservices in a wireless communication system (WCS) capable of bothunicast and multicast signaling. The apparatus includes means fordetermining whether a content can be delivered via unicast transmissionand multicast transmission. The apparatus includes means forprovisioning the unicast transmission and multicast transmission inresponse to determining the content can be delivered via unicasttransmission and multicast transmission. The apparatus includes meansfor switching between the unicast transmission and the multicasttransmission.

In another aspect, a computer program product includes acomputer-readable medium storing code for causing at least one computerto: determine whether a content can be delivered via unicasttransmission and multicast transmission; provision the unicasttransmission and multicast transmission in response to determining thecontent can be delivered via unicast transmission and multicasttransmission; and switch between the unicast transmission and themulticast transmission.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram conceptually illustrating an example of atelecommunications system.

FIG. 2 is a block diagram conceptually illustrating an example of a downlink frame structure in a telecommunications system.

FIG. 3 is a block diagram conceptually illustrating a design of a basestation/eNB and a UE configured according to one aspect of the presentdisclosure.

FIG. 4 is a diagram of a signaling frame illustrating an example ofsymbol allocation for unicast and multicast signals.

FIG. 5 is a diagram illustrating MBMS over a Single Frequency Network(MBSFN) areas within an MBSFN service area.

FIGS. 6A-B are block diagrams illustrating components of wirelesscommunication systems for providing or supporting MBSFN service.

FIG. 7 illustrates an embodiment of a methodology for managing amulticast service in a wireless communications system.

FIG. 8 is a state diagram illustrating active and inactive states of amulticast session.

FIGS. 9A-B illustrate unicast and eMBMS capacity comparisons.

FIG. 10 is a block diagram illustrating components of a wirelesscommunication system for providing or supporting seamless transitionbetween MBMS and unicast service based on a demand for a content.

FIG. 11 is a sequence diagram illustrating activities by variouscomponents of a wireless communications system implementing orsupporting a demand-based multicast service, according to embodimentsimplementing seamless transition from unicast to broadcast service.

FIG. 12 is a sequence diagram illustrating activities by variouscomponents of a wireless communications system implementing orsupporting a demand-based multicast service, according to embodimentsimplementing seamless transition from broadcast to unicast service.

FIG. 13 is another block diagram illustrating components of anotherwireless communication system for providing or supporting seamlesstransition between MBMS and unicast service based on demand for acontent.

FIG. 14 is a sequence diagram illustrating activities by variouscomponents of the another wireless communications system implementing orsupporting a demand-based multicast service, according to embodimentsimplementing seamless transition from unicast to broadcast service.

FIG. 15 is a sequence diagram illustrating activities by variouscomponents of the another wireless communications system implementing orsupporting a demand-based multicast service, according to embodimentsimplementing seamless transition from broadcast to unicast service.

FIG. 16 is a table illustrating a comparison between the methodsillustrated in FIG. 10 (Option 1) and FIG. 13 (Option 2).

FIG. 17 is a block diagram illustrating components of another wirelesscommunication system for providing or supporting seamless transitionbetween MBMS and unicast service based on demand for a content.

FIG. 18 is a block diagram illustrating components of yet anotherwireless communication system for providing or supporting seamlesstransition between MBMS and unicast service based on demand for acontent.

FIG. 19 is a another block diagram illustrating components of a wirelesscommunication system for providing or supporting seamless transitionbetween MBMS and unicast service based on a demand for a content.

FIG. 20 is a sequence diagram illustrating activities by variouscomponents of a wireless communication system implementing or supportinga demand-based multicast service, in accordance with the embodiment ofFIG. 19.

FIG. 21 is a sequence diagram illustrating activities by variouscomponents of a wireless communication system providing or supportingNetwork Provided Location Information (NetLoc) location determination.

FIG. 22 is a sequence diagram illustrating activities by variouscomponents of a wireless communications system for a UE-based solutionon switching from unicast to broadcast when the unicast and broadcastare on the same frequency.

FIG. 23 is a sequence diagram illustrating activities by variouscomponents of a wireless communications system for a UE-based solutionon switching from unicast to broadcast when the unicast and broadcastare on different frequencies.

FIG. 24 is a sequence diagram illustrating activities by variouscomponents of a wireless communications system for a UE-based solutionon switching from broadcast to unicast.

FIG. 25 illustrates switching from UC to BC (as an example, DynamicAdaptive Streaming over HTTP (DASH) may be used).

FIG. 26 illustrates switching from BC to UC.

FIG. 27 illustrates various methods for content delivery.

FIG. 28 is a sequence diagram illustrating activities by variouscomponents of a wireless communications system for switching from UC toBC mode.

FIG. 29 is a sequence diagram illustrating activities by variouscomponents of a wireless communications system for switching from BC toUC mode.

FIG. 30 illustrates switching from BC to UC (DASH may be used for bothUC and BC).

FIG. 31 illustrates switching from non-eMBMS UC to BC, where real-timetransport protocol (RTP) may be used in both delivery of content via UCand delivery of content via BC.

FIG. 32 illustrates switching from eMBMS UC to BC, where real-timetransport protocol (RTP) may be used in both delivery of content via UCand delivery of content via BC.

FIG. 33 illustrates switching from BC to UC, where real-time transportprotocol (RTP) may be used in both delivery of content via UC anddelivery of content via BC.

FIGS. 34A-E illustrate embodiments of a methodology for implementing ademand-based multicast service in a wireless communication system usinga high attach rate detection (HARD) module.

FIG. 35 illustrates an embodiment of a methodology for implementingUE-based solution for demand-based multicast service in a wirelesscommunication system.

FIGS. 36A-E illustrate embodiments of an apparatus for implementing ademand-based multicast service, in accordance with the methodologies ofFIGS. 34A-E.

FIG. 37 illustrates an embodiment of an apparatus for implementing ademand-based multicast service, in accordance with the methodology ofFIG. 35.

FIG. 38 illustrates an embodiment of another methodology forimplementing a demand-based multicast service in a wirelesscommunication system using a HARD module.

FIG. 39 illustrates an embodiment of another apparatus for implementinga demand-based multicast service, in accordance with the methodology ofFIG. 38.

FIG. 40 illustrates a relational mapping for data elements of a userservice bundle.

FIGS. 41A-B illustrate embodiments of a methodology for implementing ademand-based multicast service in a wireless communication system usingan simplified HARD (S-HARD) module.

FIG. 42 illustrates embodiments of a methodology for implementingUE-based solution for demand-based multicast service in a wirelesscommunication system.

FIGS. 43A-B illustrate embodiments of an apparatus for implementing ademand-based multicast service, in accordance with the methodologies ofFIGS. 41A-B.

FIG. 44 illustrates an embodiment of an apparatus for implementing ademand-based multicast service, in accordance with the methodology ofFIG. 42.

FIG. 45 illustrates an embodiment of a methodology for implementingswitching between UC and BC in a multi-band/multi-frequency wirelesscommunication system.

FIG. 46 illustrates an embodiment of a methodology for implementingswitching between UC and BC by a UE.

FIG. 47 illustrates another embodiment of a methodology for implementingswitching between UC and BC by a UE.

FIG. 48 illustrates an embodiment of a methodology for signaling andnetwork support for implementing switching between UC and BC.

FIG. 49 illustrates an embodiment of a methodology for provisioning BCand UC services, and switching between the BC and UC services.

FIG. 50 illustrates an embodiment of an apparatus for implementingswitching between UC and BC in a multi-band/multi-frequency wirelesscommunication system, in accordance with the methodology of FIG. 45.

FIG. 51 illustrates an embodiment of an apparatus for implementingswitching between UC and BC by a UE, in accordance with the methodologyof FIG. 46.

FIG. 52 illustrates another embodiment of an apparatus for implementingswitching between UC and BC by a UE, in accordance with the methodologyof FIG. 47.

FIG. 53 illustrates an embodiment of an apparatus for signaling andnetwork support for implementing switching between UC and BC, inaccordance with the methodology of FIG. 48.

FIG. 54 illustrates an embodiment of an apparatus for provisioning BCand UC services, and switching between the BC and UC services, inaccordance with the methodology of FIG. 49.

DETAILED DESCRIPTION

The detailed description set forth below, in connection with theappended drawings, is intended as a description of variousconfigurations and is not intended to represent the only configurationsin which the concepts described herein may be practiced. The detaileddescription includes specific details for the purpose of providing athorough understanding of the various concepts. However, it will beapparent to those skilled in the art that these concepts may bepracticed without these specific details. In some instances, well-knownstructures and components are shown in block diagram form in order toavoid obscuring such concepts.

The techniques described herein may be used for various wirelesscommunication networks such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA andother networks. The terms “network” and “system” are often usedinterchangeably. A CDMA network may implement a radio technology such asUniversal Terrestrial Radio Access (UTRA), CDMA2000, etc. UTRA includesWideband CDMA (WCDMA) and other variants of CDMA. CDMA2000 coversIS-2000, IS-95 and IS-856 standards. A TDMA network may implement aradio technology such as Global System for Mobile Communications (GSM).An OFDMA network may implement a radio technology such as Evolved UTRA(E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16(WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA and E-UTRA are part ofUMTS. 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are newreleases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A and GSMare described in documents from an organization named “3rd GenerationPartnership Project” (3GPP). CDMA2000 and UMB are described in documentsfrom an organization named “3rd Generation Partnership Project 2”(3GPP2). The techniques described herein may be used for the wirelessnetworks and radio technologies mentioned above as well as otherwireless networks and radio technologies. For clarity, certain aspectsof the techniques are described below for LTE, and LTE terminology isused in much of the description below.

FIG. 1 shows a wireless communication network 100, which may be an LTEnetwork. The wireless network 100 may include a number of eNBs 110 andother network entities. An eNB may be a station that communicates withthe UEs and may also be referred to as a base station, a Node B, anaccess point, or other term. Each eNB 110 a, 110 b, 110 c may providecommunication coverage for a particular geographic area. In 3GPP, theterm “cell” can refer to a coverage area of an eNB and/or an eNBsubsystem serving this coverage area, depending on the context in whichthe term is used.

An eNB may provide communication coverage for a macro cell, a pico cell,a femto cell, and/or other types of cell. A macro cell may cover arelatively large geographic area (e.g., several kilometers in radius)and may allow unrestricted access by UEs with service subscription. Apico cell may cover a relatively small geographic area and may allowunrestricted access by UEs with service subscription. A femto cell maycover a relatively small geographic area (e.g., a home) and may allowrestricted access by UEs having association with the femto cell (e.g.,UEs in a Closed Subscriber Group (CSG), UEs for users in the home,etc.). An eNB for a macro cell may be referred to as a macro eNB. An eNBfor a pico cell may be referred to as a pico eNB. An eNB for a femtocell may be referred to as a femto eNB or a home eNB (HNB). In theexample shown in FIG. 1, the eNBs 110 a, 110 b and 110 c may be macroeNBs for the macro cells 102 a, 102 b and 102 c, respectively. The eNB110 x may be a pico eNB for a pico cell 102 x, serving a UE 120 x. TheeNBs 110 y and 110 z may be femto eNBs for the femto cells 102 y and 102z, respectively. An eNB may support one or multiple (e.g., three) cells.

The wireless network 100 may also include relay stations 110 r. A relaystation is a station that receives a transmission of data and/or otherinformation from an upstream station (e.g., an eNB or a UE) and sends atransmission of the data and/or other information to a downstreamstation (e.g., a UE or an eNB). A relay station may also be a UE thatrelays transmissions for other UEs. In the example shown in FIG. 1, arelay station 110 r may communicate with the eNB 110 a and a UE 120 r inorder to facilitate communication between the eNB 110 a and the UE 120r. A relay station may also be referred to as a relay eNB, a relay, orother terminology.

The wireless network 100 may be a heterogeneous network that includeseNBs of different types, e.g., macro eNBs, pico eNBs, femto eNBs,relays, etc. These different types of eNBs may have different transmitpower levels, different coverage areas, and different impact oninterference in the wireless network 100. For example, macro eNBs mayhave a high transmit power level (e.g., 20 Watts) whereas pico eNBs,femto eNBs and relays may have a lower transmit power level (e.g., 1Watt).

The wireless network 100 may support synchronous or asynchronousoperation. For synchronous operation, the eNBs may have similar frametiming, and transmissions from different eNBs may be approximatelyaligned in time. For asynchronous operation, the eNBs may have differentframe timing, and transmissions from different eNBs may not be alignedin time. The techniques described herein may be used for bothsynchronous and asynchronous operation.

A network controller 130 may couple to a set of eNBs and providecoordination and control for these eNBs. The network controller 130 maycommunicate with the eNBs 110 via a backhaul. The eNBs 110 may alsocommunicate with one another, e.g., directly or indirectly via wirelessor wireline backhaul.

The UEs 120 may be dispersed throughout the wireless network 100, andeach UE may be stationary or mobile. A UE may also be referred to as aterminal, a mobile station, a subscriber unit, a station, mobile entity,or other terminology. A UE may be a cellular phone, a personal digitalassistant (PDA), a wireless modem, a wireless communication device, ahandheld device, a laptop computer, a cordless phone, a wireless localloop (WLL) station, or other mobile entities. A UE may be able tocommunicate with macro eNBs, pico eNBs, femto eNBs, relays, or othernetwork entities. In FIG. 1, a solid line with double arrows indicatesdesired transmissions between a UE and a serving eNB, which is an eNBdesignated to serve the UE on the downlink and/or uplink. A dashed linewith double arrows indicates interfering transmissions between a UE andan eNB.

LTE utilizes orthogonal frequency division multiplexing (OFDM) on thedownlink and single-carrier frequency division multiplexing (SC-FDM) onthe uplink. OFDM and SC-FDM partition the system bandwidth into multiple(K) orthogonal subcarriers, which are also commonly referred to astones, bins, or other terminology. Each subcarrier may be modulated withdata. In general, modulation symbols are sent in the frequency domainwith OFDM and in the time domain with SC-FDM. The spacing betweenadjacent subcarriers may be fixed, and the total number of subcarriers(K) may be dependent on the system bandwidth. For example, K may beequal to 128, 256, 512, 1024 or 2048 for system bandwidth of 1.25, 2.5,5, 10 or 20 megahertz (MHz), respectively. The system bandwidth may alsobe partitioned into sub-bands. For example, a sub-band may cover 1.08MHz, and there may be 1, 2, 4, 8 or 16 sub-bands for system bandwidth of1.25, 2.5, 5, 10 or 20 MHz, respectively.

FIG. 2 shows a down link frame structure 200 used in LTE. Thetransmission timeline for the downlink may be partitioned into units ofradio frames 202, 204, 206. Each radio frame may have a predeterminedduration (e.g., 10 milliseconds (ms)) and may be partitioned into 10subframes 208 with indices of 0 through 9. Each subframe may include twoslots, e.g., slots 210. Each radio frame may thus include 20 slots withindices of 0 through 19. Each slot may include L symbol periods, e.g., 7symbol periods 212 for a normal cyclic prefix (CP), as shown in FIG. 2,or 6 symbol periods for an extended cyclic prefix. The normal CP andextended CP may be referred to herein as different CP types. The 2Lsymbol periods in each subframe may be assigned indices of 0 through2L−1. The available time frequency resources may be partitioned intoresource blocks. Each resource block may cover N subcarriers (e.g., 12subcarriers) in one slot.

In LTE, an eNB may send a primary synchronization signal (PSS) and asecondary synchronization signal (SSS) for each cell in the eNB. Theprimary and secondary synchronization signals may be sent in symbolperiods 6 and 5, respectively, in each of subframes 0 and 5 of eachradio frame with the normal cyclic prefix, as shown in FIG. 2. Thesynchronization signals may be used by UEs for cell detection andacquisition. The eNB may send a Physical Broadcast Channel (PBCH) insymbol periods 0 to 3 in slot 1 of subframe 0. The PBCH may carrycertain system information.

The eNB may send a Physical Control Format Indicator Channel (PCFICH) inonly a portion of the first symbol period of each subframe, althoughdepicted in the entire first symbol period in FIG. 2. The PCFICH mayconvey the number of symbol periods (M) used for control channels, whereM may be equal to 1, 2 or 3 and may change from subframe to subframe. Mmay also be equal to 4 for a small system bandwidth, e.g., with lessthan 10 resource blocks. In the example shown in FIG. 2, M=3. The eNBmay send a Physical HARQ Indicator Channel (PHICH) and a PhysicalDownlink Control Channel (PDCCH) in the first M symbol periods of eachsubframe (M=3 in FIG. 2). The PHICH may carry information to supporthybrid automatic retransmission (HARQ). The PDCCH may carry informationon resource allocation for UEs and control information for downlinkchannels. Although not shown in the first symbol period in FIG. 2, it isunderstood that the PDCCH and PHICH are also included in the firstsymbol period. Similarly, the PHICH and PDCCH are also both in thesecond and third symbol periods, although not shown that way in FIG. 2.The eNB may send a Physical Downlink Shared Channel (PDSCH) in theremaining symbol periods of each subframe. The PDSCH may carry data forUEs scheduled for data transmission on the downlink. The various signalsand channels in LTE are described in 3GPP TS 36.211, entitled “EvolvedUniversal Terrestrial Radio Access (E-UTRA); Physical Channels andModulation,” which is publicly available.

The eNB may send the PSS, SSS and PBCH in the center 1.08 MHz of thesystem bandwidth used by the eNB. The eNB may send the PCFICH and PHICHacross the entire system bandwidth in each symbol period in which thesechannels are sent. The eNB may send the PDCCH to groups of UEs incertain portions of the system bandwidth. The eNB may send the PDSCH tospecific UEs in specific portions of the system bandwidth. The eNB maysend the PSS, SSS, PBCH, PCFICH and PHICH in a broadcast manner to allUEs, may send the PDCCH in a unicast manner to specific UEs, and mayalso send the PDSCH in a unicast manner to specific UEs.

A number of resource elements may be available in each symbol period.Each resource element may cover one subcarrier in one symbol period andmay be used to send one modulation symbol, which may be a real orcomplex value. Resource elements not used for a reference signal in eachsymbol period may be arranged into resource element groups (REGs). EachREG may include four resource elements in one symbol period. The PCFICHmay occupy four REGs, which may be spaced approximately equally acrossfrequency, in symbol period 0. The PHICH may occupy three REGs, whichmay be spread across frequency, in one or more configurable symbolperiods. For example, the three REGs for the PHICH may all belong insymbol period 0 or may be spread in symbol periods 0, 1 and 2. The PDCCHmay occupy 9, 18, 32 or 64 REGs, which may be selected from theavailable REGs, in the first M symbol periods. Only certain combinationsof REGs may be allowed for the PDCCH.

A UE may know the specific REGs used for the PHICH and the PCFICH. TheUE may search different combinations of REGs for the PDCCH. The numberof combinations to search is typically less than the number of allowedcombinations for the PDCCH. An eNB may send the PDCCH to the UE in anyof the combinations that the UE will search.

A UE may be within the coverage of multiple eNBs. One of these eNBs maybe selected to serve the UE. The serving eNB may be selected based onvarious criteria such as received power, path loss, signal-to-noiseratio (SNR), etc.

FIG. 3 shows a block diagram of a design of a base station/eNB 110 and aUE 120, which may be one of the base stations/eNBs and one of the UEs inFIG. 1. For a restricted association scenario, the base station 110 maybe the macro eNB 110 c in FIG. 1, and the UE 120 may be the UE 120 y.The base station 110 may also be a base station of some other type. Thebase station 110 may be equipped with antennas 334 a through 334 t, andthe UE 120 may be equipped with antennas 352 a through 352 r.

At the base station 110, a transmit processor 320 may receive data froma data source 312 and control information from a controller/processor340. The control information may be for the PBCH, PCFICH, PHICH, PDCCH,or other control channel. The data may be for the PDSCH, or other datachannel. The processor 320 may process (e.g., encode and symbol map) thedata and control information to obtain data symbols and control symbols,respectively. The processor 320 may also generate reference symbols,e.g., for the PSS, SSS, and cell-specific reference signal. A transmit(TX) multiple-input multiple-output (MIMO) processor 330 may performspatial processing (e.g., precoding) on the data symbols, the controlsymbols, and/or the reference symbols, if applicable, and may provideoutput symbol streams to the modulators (MODS) 332 a through 332 t. Eachmodulator 332 may process a respective output symbol stream (e.g., forOFDM, etc.) to obtain an output sample stream. Each modulator 332 mayfurther process (e.g., convert to analog, amplify, filter, andupconvert) the output sample stream to obtain a downlink signal.Downlink signals from modulators 332 a through 332 t may be transmittedvia the antennas 334 a through 334 t, respectively.

At the UE 120, the antennas 352 a through 352 r may receive the downlinksignals from the base station 110 and may provide received signals tothe demodulators (DEMODs) 354 a through 354 r, respectively. Eachdemodulator 354 may condition (e.g., filter, amplify, downconvert, anddigitize) a respective received signal to obtain input samples. Eachdemodulator 354 may further process the input samples (e.g., for OFDM,etc.) to obtain received symbols. A MIMO detector 356 may obtainreceived symbols from all the demodulators 354 a through 354 r, performMIMO detection on the received symbols if applicable, and providedetected symbols. A receive processor 358 may process (e.g., demodulate,deinterleave, and decode) the detected symbols, provide decoded data forthe UE 120 to a data sink 360, and provide decoded control informationto a controller/processor 380. The processor 380 may also perform ordirect the execution of the functional blocks illustrated in processesfor performance by a UE according to the techniques described herein.

On the uplink, at the UE 120, a transmit processor 364 may receive andprocess data (e.g., for the PUSCH) from a data source 362 and controlinformation (e.g., for the PUCCH) from the controller/processor 380. Theprocessor 364 may also generate reference symbols for a referencesignal. The symbols from the transmit processor 364 may be precoded by aTX MIMO processor 366 if applicable, further processed by the modulators354 a through 354 r (e.g., for SC-FDM, etc.), and transmitted to thebase station 110. At the base station 110, the uplink signals from theUE 120 may be received by the antennas 334, processed by thedemodulators 332, detected by a MIMO detector 336 if applicable, andfurther processed by a receive processor 338 to obtain decoded data andcontrol information sent by the UE 120. The processor 338 may providethe decoded data to a data sink 339 and the decoded control informationto the controller/processor 340.

The controllers/processors 340 and 380 may direct the operation at thebase station 110 and the UE 120, respectively. The processor 340 and/orother processors and modules at the base station 110 may perform ordirect the execution of various processes for the techniques describedherein. The processor 380 and/or other processors and modules at the UE120 may also perform or direct the execution of various processes forthe techniques described herein. The memories 342 and 382 may store dataand program codes for the base station 110 and the UE 120, respectively.A scheduler 344 may schedule UEs for data transmission on the downlinkand/or uplink. Other aspects of the techniques described herein may beperformed by other network entities of a wireless communications systemas described elsewhere herein.

One mechanism to facilitate high bandwidth communication for multimediahas been single frequency network (SFN) operation. Particularly,Multimedia Broadcast Multicast Service (MBMS) and MBMS for LTE, alsoknown as evolved MBMS (eMBMS) (including, for example, what has recentlycome to be known as multimedia broadcast single frequency network(MBSFN) in the LTE context), can utilize such SFN operation. SFNsutilize radio transmitters, such as, for example, eNBs, to communicatewith subscriber UEs. Groups of eNBs can transmit information in asynchronized manner, so that signals reinforce one another rather thaninterfere with each other at the receiver. In the context of eMBMS, theshared content is transmitted from multiple eNBs of an LTE network tomultiple UEs. Therefore, within a given eMBMS area, a UE may receiveeMBMS signals from any eNB (or eNBs) within radio range. However, todecode the eMBMS signal each UE receives Multicast Control Channel(MCCH) information from a serving eNB over a non-eMBMS channel. MCCHinformation changes from time to time and notification of changes isprovided through another non-eMBMS channel, the PDCCH. Therefore, todecode eMBMS signals within a particular eMBMS area, each UE is servedMCCH and PDCCH signals by one of the eNBs in the area.

In accordance with aspects of the subject of this disclosure, there isprovided a wireless network (e.g., a 3GPP network) having featuresrelating to single carrier optimization for eMBMS. eMBMS provides anefficient way to transmit shared content from an LTE network to multiplemobile entities, such as, for example, UEs.

With respect to a physical layer (PHY) of eMBMS for LTE FrequencyDivision Duplex (FDD), the channel structure may comprise time divisionmultiplexing (TDM) resource partitioning between an eMBMS and unicasttransmissions on mixed carriers, thereby allowing flexible and dynamicspectrum utilization. Currently, a subset of subframes (up to 60%),known as multimedia broadcast single frequency network (MBSFN)subframes, can be reserved for eMBMS transmission. As such current eMBMSdesign allows at most six out of ten subframes for eMBMS.

An example of subframe allocation for eMBMS is shown in FIG. 4, whichshows an existing allocation of MBSFN reference signals on MBSFNsubframes 400, for a single-carrier case. Components depicted in FIG. 4correspond to those shown in FIG. 2, with FIG. 4 showing the individualsubcarriers within each slot 402 and resource block (RB) 404. In 3GPPLTE, a RB 404 spans 12 subcarriers over a slot duration of 0.5 ms, witheach subcarrier having a bandwidth of 15 kHz together spanning 180 kHzper RB. Subframes may be allocated for unicast or eMBMS; for example ina sequence of subframes 408 labeled 0, 1, 2, 3, 4, 5, 6, 7, 8, and 9,subframes 0, 4, 5, and 9 may be excluded from eMBMS in FDD. Subframes 0,1, 5, and 6 may be excluded from eMBMS in time division duplex (TDD).More specifically, subframes 0, 4, 5, and 9 may be used forPSS/SSS/PBCH/paging/system information blocks (SIBS) and unicastservice. Remaining subframes in the sequence, e.g., subframes 1, 2, 3,6, 7, and 8 may be configured as eMBMS subframes.

With continued reference to FIG. 4, within each eMBMS subframe 400, thefirst 1 or 2 symbols may be used for unicast reference symbols (RSs) andcontrol signaling. A CP length of the first 1 or 2 symbols may followthat of subframe 0. A transmission gap may occur between the first 1 or2 symbols and the eMBMS symbols if the CP lengths are different inadjacent subframes. In related aspects, the overall eMBMS bandwidthutilization may be 42.5% considering RS overhead (e.g., 6 eMBMSsubframes and 2 control symbols within each eMBMS subframe). Knowntechniques for providing MBSFN RSs and unicast RSs typically involveallocating the MBSFN RSs on MBSFN subframes (as shown in FIG. 4), andseparately allocating unicast RSs on non-MBSFN subframes. Morespecifically, as FIG. 4 shows, the extended CP of the MBSFN subframe 400includes MBSFN RSs 410 but not unicast RSs. The present technology isnot limited to the particular frame allocation scheme illustrated byFIGS. 2 and 4, which are presented by way of example, and not by way oflimitation. A multicast session (which may sometimes also be referred toas a multicast broadcast) may use any suitable frame allocation scheme.Multicast and broadcast may be used interchangeably in this disclosure.

FIG. 5 illustrates a system 500 including an MBMS service area 502encompassing multiple MBSFN areas 504, 506, 508, which themselvesinclude multiple cells or base stations 510. As used herein, an “MBMSservice area” refers to a group of wireless transmission cells where acertain MBMS service is available. For example, a particular sports orother program may be broadcast by base stations within the MBMS servicearea at a particular time. The area where the particular program isbroadcast defines the MBMS service area. The MBMS service area may bemade up of one or more “MBSFN areas” as shown at 504, 506 and 508. Asused herein, an MBSFN area refers to a group of cells (e.g., cells 510)currently broadcasting a particular program in a synchronized mannerusing an MBSFN protocol. An “MBSFN synchronization area” refers to agroup of cells that are interconnected and configured in a way such thatthey are capable of operating in a synchronized fashion to broadcast aparticular program using an MBSFN protocol, regardless of whether or notthey are currently doing so. Each eNB can belong to only one MBSFNsynchronization area, on a given frequency layer. It is worth notingthat an MBMS service area 502 may include one or more MBSFNsynchronization areas (not shown). Conversely, an MBSFN synchronizationarea may include one or more MBSFN areas or MBMS service areas.Generally, an MBSFN area is made up of all, or a portion of, a singleMBSFN synchronization area and is located within a single MBMS servicearea. Overlap between various MBSFN areas is supported, and a single eNBmay belong to several different MBSFN areas. For example, up to 8independent MCCHs may be configured in System Information Block (SIB) 13to support membership in different MBSFN areas. An MBSFN Area ReservedCell or Base Station is a cell/base station within a MBSFN Area thatdoes not contribute to the MBSFN transmission, for example a cell near aMBSFN Synchronization Area boundary, or a cell that that is not neededfor MBSFN transmission because of its location.

FIG. 6A illustrates functional entities of a wireless communicationsystem 600 for providing or supporting MBSFN service. Regarding Qualityof Service (QoS), the system 600 uses a Guaranteed Bit Rate (GBR) typeMBMS bearer, wherein the Maximum Bit Rate (MBR) equals the GBR. Thesecomponents are shown and described by way of example, and do not limitthe inventive concepts described herein, which may be adapted to otherarchitectures and functional distributions for delivering andcontrolling multicast transmissions.

The system 600 may include an MBMS Gate Way (MBMS GW) 616. The MBMS GW616 controls Internet Protocol (IP) multicast distribution of MBMS userplane data to eNBs 604 via an M1 interface; one eNB 604 of many possibleeNBs is shown, wherein “M1” refers to a logical interface as describedby technical specifications for LTE and related specifications. Inaddition, the MBMS GW controls IP multicast distribution of MBMS userplane data to UTRAN Radio Network Controllers (RNCs) 620 via an M1interface; one UTRAN RNC 620 of many possible RNCs is shown. The M1interface is associated to MBMS data (user plane) and makes use of IPfor delivery of data packets. The eNB 604 may provide MBMS content to aUE 602 via an E-UTRAN Uu interface, wherein “Uu” refers to an airinterface as described by technical specifications for LTE and relatedspecifications. The RNC 620 may provide MBMS content to a UE 622 via aUu interface. The MBMS GW 616 may further perform MBMS Session ControlSignaling, for example MBMS session start and session stop, via theMobility Management Entity (MME) 608 and Sm interface, wherein “Sm”refers to a logical interface as described by technical specificationsfor LTE and related specifications. The MBMS GW 616 may further providean interface for entities using MBMS bearers through the SG-mb (userplane) reference point, and provide an interface for entities using MBMSbearers through the SGi-mb (control plane) reference point, wherein“SG-mb” and “SGi-mb” refer to logical interfaces as described bytechnical specifications for LTE and related specifications. The SG-mbInterface carries MBMS bearer service specific signaling. The SGi-mbinterface is a user plane interface for MBMS data delivery. MBMS datadelivery may be performed by IP unicast transmission, which may be adefault mode, or by IP multicasting. The MBMS GW 616 may provide acontrol plane function for MBMS over UTRAN via a Serving General PacketRadio Service Support Node (SGSN) 618 and the Sn/Iu interfaces.

The system 600 may further include a Multicast Coordinating Entity (MCE)606. The MCE 606 may perform an admission control function for MBMScontent, and allocate time and frequency radio resources used by alleNBs in the MBSFN area for multi-cell MBMS transmissions using MBSFNoperation. The MCE 606 may determine a radio configuration for an MBSFNArea, such as, for example, the modulation and coding scheme. The MCE606 may schedule and control user plane transmission of MBMS content,and manage eMBMS service multiplexing, by determining which services areto be multiplexed in which Multicast Channel (MCH). The MCE 606 mayparticipate in MBMS Session Control Signaling with the MME 608 throughan M3 interface, and may provide a control plane interface M2 with theeNB 604, wherein “M2” and “M3” refer to logical interfaces as describedby technical specifications for LTE and related specifications.

The system 600 may further include a Broadcast-Multicast Service Center(BM-SC) 612 in communication with a content provider server 614. TheBM-SC 612 may handle intake of multicast content from one or moresources such as the content provider 614, and provide other higher-levelmanagement functions as described below. These functions may include,for example, a membership function, including authorization andinitiation of MBMS services for an identified UE. The BM-SC 612 mayfurther perform MBMS session and transmission functions, scheduling oflive broadcasts, and delivery, including MBMS and associated deliveryfunctions. The BM-SC 612 may further provide service advertisement anddescription, such as advertising content available for multicast. Aseparate Packet Data Protocol (PDP) context may be used to carry controlmessages between a UE and a BM-SC. The BM-SC may further providesecurity functions such as key management, manage charging of contentproviders according to parameters such as data volume and QoS, providecontent synchronization for MBMS in UTRAN and in E-UTRAN for broadcastmode, and provide header compression for MBSFN data in UTRAN. The BM-SC612 may indicate session start, update and stop to the MBMS-GW 616including session attributes such as QoS and MBMS service area.

The system 600 may further include a Mobility Management Entity (MME)608 in communication with the MCE 606 and MBMS-GW 616. The MME 608 mayprovide a control plane function for MBMS over E-UTRAN. In addition, theMME may provide the eNB 604 with multicast related information definedby the MBMS-GW 616. An Sm interface between the MME 608 and the MBMS-GW616 may be used to carry MBMS control signaling, for example, sessionstart and stop signals.

The system 600 may further include a Packet Data Network (PDN) Gate Way(GW) 610, sometimes abbreviated as a P-GW. The P-GW 610 may provide anEvolved Packet System (EPS) bearer between the UE 602 and BM-SC 612 forsignaling and/or user data. As such, the P-GW may receive UniformResource Locator (URL) based requests originating from UEs inassociation with IP addresses assigned to the UEs. The BM-SC 612 mayalso be linked to one or more content providers via the P-GW 610, whichmay communicate with the BM-SC 612 via an IP interface.

An alternative system 600′ as shown in FIG. 6B may utilize a networkentity that may be referred to, for example, as a high attach ratedetection (HARD) module 624. The system 600′ is similar to system 600shown in FIG. 6A, and uses the same reference numerals for correspondingelements. The HARD module 624 may be an additional distinct networkentity, or it may be incorporated into, for example, the P-GW 610, theBM-SC 612 (e.g., as a logical entity), traffic detection function (TDF)(not shown in the figure), or the content provider 614. If the HARDmodule 624 is implemented as a distinct network entity, it may belocated, for example, between the P-GW 610 and the BM-SC 612; however,other arrangements are also possible. Further details regarding thealternative system 600′ are discussed in the disclosure below inconnection with demand monitoring.

Either of the systems 600 and 600′ may be used to transmit an eMBMS orother multicast session in an MBMS area. As shown in FIG. 7, a method700 for handling an MBMS session may include an initial operation 702 ofannouncing or advertising availability of a scheduled transmission. Forexample, an MBMS broadcast of a sporting event may be advertised in aspecified area to begin at a certain date and time, for further exampleby using an Open Mobile Alliance (OMA) Mobile Broadcast Services EnablerSuite (BCAST) service guide. To obtain advertising, users may subscribeto a message service, download a program guide or listing, or take someother action. In the alternative, advertising may be pushed to mobileentities without requiring any action from the user. A serviceannouncement may include, for example, a service identifier, servicearea identifier, schedule, applicable IP multicast address(es), andother information.

At 704, the system may initiate a multicast transmission at theadvertised date and time, within the specified broadcast area. Forexample, a BM-SC may initiate an MBMS broadcast service using a sessionstart procedure to establish an MBMS radio bearer.

At 706, the system may provide a notification of ongoing or forthcomingMBMS services to a mobile entity, such as, for example, by using an MCCHchange notification transmitted to the mobile entity. At 708, the systemtransmits MBMS content for the advertised service, using the establishedMBMS radio bearer. At 710, once the eMBMS broadcast is completed, thesystem stops the multicast session and releases its associated radiobearer.

An MBMS bearer context may be created in the MME, MBMS GW, SGSN andother elements of a Radio Access Network (RAN) upon initiation of anMBMS session. FIG. 8 illustrates a state cycle 800 between an activesession state 820 and a standby state 810 of an MBMS bearer context. TheMBMS bearer context itself may include an MBMS GW Tunnel Endpoint ID forControl plane (TEID-C) and a Temporary Mobile Group Identity (TMGI). Aunique TMGI per MBMS bearer service may be allocated by the BM-SC, andused for MBMS notification purpose. The MBMS bearer context may furtherinclude a Flow Identifier; an MBMS GW IP Address for Control Plane inuse; an MBMS GW IP Address for User Plane in use; and a Common TunnelEndpoint ID (C-TEID) of the MBMS GW for the user plane. The MBMS bearercontext may further include one or more QoS indicators or parameters,for example, a QoS Class Identifier (QCI), or MBR=GBR as mentionedabove. The MBMS bearer context may further include an MBMS Service Areaidentifier; a list of downstream nodes; and an IP multicast and Sourceaddress for distribution, which may be selected by the MBMS GW. Theforegoing MBMS bearer context components are provided by way of exampleonly, and the present technology is not limited to a particularconfiguration of MBMS bearer context.

In LTE, an eMBMS application may be classified as schedule based eMBMSapplication or a demand based eMBMS application. In a schedule basedeMBMS application, a system operator on the network side controlstransmission of eMBMS content, which occurs at a scheduled time. Amobile entity may subscribe to the scheduled transmission and therebyreceive content of interest to the mobile user. The Multi-MediaBroadcast over a Single Frequency Network (MBSFN) is activated based ona pre-scheduled time slot. The service guide is made available fordownload by UEs prior to start of the service. Further, the UEs that areinterested in the content tune to the designated eMBMS channel based onservice schedule. Content offerings available to UEs via EMBMStransmission are limited to the operator's scheduled eMBMS offerings.

In a demand based eMBMS application, eMBMS content offerings areprovided in response to demand monitoring. The network may switchdelivery of content between unicast (UC) delivery and MBMS (or BC) modeof delivery based on user demand. When the network detects that demandfor a content has a high attach rate (e.g., number of the UEs that arereceiving a content from the same area exceeds a configurable thresholdbased on operator policy), the network may turn on MBMS mode, and switchcontent delivery from UC delivery to MBMS mode of content delivery. Whenthe network detects demand for the content has a low attach rate (e.g.,number of UEs that are receiving a content from the same area dropsbelow a configurable threshold based on operator policy), the networkmay turn off the MBMS mode of content delivery, and the user maycontinue receiving the content through unicast delivery. For example,users may search and request content available over a wide-area network,such as the Internet. The system monitors demand levels for specificcontent from the same areas, and detects demand that exceeds a specifiedthreshold. This threshold may float in response to current load levelsor other parameters. In response to detecting demand in excess of thethreshold, the system may provide the demanded content via an eMBMSsession and, as necessary, transition mobile entities from separatelycontrolled unicast sessions to a common eMBMS broadcast for the contentwithin a specified network area, e.g., an MBMS service area, or MBSFNarea. Available MBMS content is not limited to predetermined contentselections broadcast by system operators on a schedule based basis. Amuch broader array of content may be available via eMBMS broadcasts tomobile entities interested in receiving the content. System operatorsmay more efficiently utilize system resources by transmitting the mostpopular content, based on user demand, in an area via multicast.

In a demand based eMBMS, the MBSFN may be activated based on userinterest. Demand-based eMBMS may require detection of the same contentaccessed by multiple unicast UEs, and activation of eMBMS to transmitthe content, and seamlessly transition from unicast to multicast mode oftransmission. Examples of content that are suitable for demand basedeMBMS may include breaking news, traffic alerts due to abnormal events,which may cause a large number of users to tune to a news channel ortraffic channel. Another example may be content/movie download via acache, where many devices/users may request from a server download ofsome content, game, or movie during a certain sliding window time periodof a predefined length. When the network detects the popularity of thecontent based on the requests, the network may decide to use MBMS modevia file download to send the content to the UEs. Dynamic AdaptiveStreaming over HTTP (DASH) for streaming may be utilized to delivercontent. The content is partitioned into one or more segments, or DASHsegments, and delivered using HTTP. Segments of the content may bedescribed in a media presentation description (MPD).

Demand based eMBMS may be further classified into two different types:(1) live broadcasting and (2) recorded on-demand broadcasting, forexample on-demand streaming or file downloading. Streaming oftelevision-like programming using IP (IP TV) and IP radio are examplesof live broadcasting types of demand based eMBMS. A characteristic oflive broadcasting is that the source streams identical content to one ormore destination addresses at substantially the same time regardless ofwhen a user initiates a streaming download, thereby emulating abroadcast of identical content to different receivers at the same time.Using a demand based methodology, mobile entities receiving orrequesting to receive particular live broadcast content may beaggregated to receive the live content via multicast when located in thesame MBSFN service area.

In comparison, a second type of demand based eMBMS—on-demand streamingor file downloading—may be characterized by the content being providedto different destinations at different times. The release of popularcontent may trigger concurrent or substantially concurrent streaming ordownloading to different addresses. For example, the popularization of avideo, or the release of a popularly anticipated application orapplication update, may cause many users to stream or download thecontent within a relatively narrow time window. Mobile entitiesreceiving or requesting identical content within shared time window, forexample, concurrent or overlapping downloading or streaming sessions,may partially or completely share bandwidth needed for the downloadingor streaming using a demand-based eMBMS session. In this type of demand,the UE may cache the content locally and the content can be consumed bythe user later per user's request.

Certain technical issues can arise in providing demand based eMBMSservice, which may be resolved using different technological solutions.One of the issues to be resolved for demand based eMBMS may includetransitioning between UC transmission and BC transmission modes so thatuser reception will be minimally impacted during the transition periodbetween UC and BC transmission. Other technical issues may also includedemand monitoring; that is, detecting mobile entities that arerequesting specific content, either by receiving the content via aunicast session, requesting to receive the content, or both. Anothertechnical issue may relate to establishing the demand based eMBMSservice in the correct area to serve the common demand. Establishing theeMBMS service in the correct area may involve detecting locations of themobile entities requesting common content. Another technical issue mayrelate to switching between unicast and multicast sessions wheninitiating or terminating a demand based eMBMS session. Anothertechnical issue may relate to indicating to the UE the association ofthe content that may be sent via UC transmission or eMBMS transmission,or both, and indicating to the UE to switch between the UC transmissionand BC transmission modes during a predefined time window. Anothertechnical issue may relate to handling a mobile entity that requestscontent that is already being broadcast in an eMBMS session in themobile entity's area. The present disclosure provides alternativetechnical solutions for addressing these and other issues related toproviding demand based eMBMS in a wireless communications system.

FIGS. 9A-B illustrate unicast and eMBMS capacity comparisons. FIGS. 9A-Bshow that eMBMS may offer higher capacity for content delivery thataverages more than one user per cell in a large SFN area deployment.FIG. 9A shows a chart 900 comparing the number of UEs per cell versusdata throughput in bits per second (bps) for multiple unicasttransmission scenarios and multiple broadcast transmission scenariosusing 3GPP D1 and D3 models. In unicast transmission, a piece ofinformation or content may be sent from a transmitting entity to areceiving entity. There may only be one transmitting entity and onereceiving entity. In broadcast transmission, a piece of information orcontent may be sent from a transmitting entity to multiple receivingentities. In this case, there may be one transmitting entity, but thepiece of information or content may be received by the multiplereceiving entities. In the two unicast transmission scenarios of FIG.9A, as the UE/cell value increases, the throughput decreases becauseeach UE requires a separate transmission of content. The separatetransmissions of content reduce transmission efficiency due to extraoverhead, scheduling requirements, etc. In the two multicasttransmission scenarios of FIG. 9A, as the UE/cell value increases, thethroughput per user remains fixed because the same transmission may bereceived by all the UEs. There is no loss of throughput for eachadditional UE in broadcast transmission. FIG. 9B shows a chart 950comparing the number of UEs per cell versus capacity in bits per second(bps) for multiple unicast transmission scenarios and multiple broadcasttransmission scenarios using other propagation models including denseurban, urban, suburban, and rural. eMBMS may be used for broadcasttransmissions. In the scenarios of FIG. 9B, analogous to the unicast andbroadcast scenarios of FIG. 9A, the capacity decreases as the UE/cellvalues increase in unicast transmission, but the capacity per user mayremain fixed as the UE/cell values increase in broadcast transmission.

FIG. 10 is a block diagram illustrating components of a wirelesscommunication system for providing or supporting seamless transitionbetween MBMS and unicast service based on demand for a content. The HARDmodule 1010 may be co-located with the P-GW 610. The seamless transitionis a transition of delivery of content to a mobile device from UC to BCor BC to UC without or with minimal service interruption. The contentprovider/internet service provider (ISP) 614 may include a DASH server1012. The system may include a unicast DASH path 1020 for transmissionof the DASH segments from the content provider/(ISP) 614 to the DASHclient 1002 in the UE 602 via the P-GW 610. The system may include abroadcast DASH path 1024 for transmission of the DASH segments from thecontent provider/ISP 614 to the Broadcast service layer 1004 in the UE602 via the DASH-proxy 1006 in the BM-SC 612, the MBMS-GW 616, and theeNB 604. A broadcast session management connection 1022 is shown indashed line between the P-GW 610, BM-SC 612, MBMS-GW 616, eNB 604, MCE606, MME 608, and HSS 1008. A broadcast service layer interface 1026 isshown between the broadcast service layer 1004 and DASH client 1002. Thewireless communication system may include a High Attach Rate Detection(HARD) module 1010. The HARD module 1010 may be co-located with the P-GW610 as illustrated in FIG. 10, or co-located with the contentprovider/ISP 614, or co-located with another network entity. Forexample, the HARD module 1010 may count the number of UEs accessing thesame service or content via a unicast transmission from the same area todetermine an aggregate demand. When the HARD module 1010 detects a highcount of UEs accessing the same service/content (“high interest”), theHARD module 1010 may inform the DASH-proxy 1006. Thereafter, the HARDmodule 1010 may notify the UE once a broadcast service is available orwhere the content is switched from unicast delivery to broadcastdelivery.

The DASH-proxy 1006 may be co-located with the BM-SC 612, a contentdelivery network (CDN), or may be a separate entity. Acting as the‘hub’, the DASH-proxy 1006 serves only the broadcast data path. TheDASH-proxy 1006 may inform the HARD module 1010 when the BC mode isstarted. The DASH-proxy 1006 may obtain a media presentation description(MPD) from the DASH server 1012 and send it to the UE (either through aservice announcement, service discovery, or unicast MPD download). TheDASH-proxy 1006 may interact with the BM-SC 612 to send the demand-basedservice on eMBMS. The UE may obtain the set of URLs that can betransitioned between Unicast and Broadcast mode from a web-server, or asprovisioned information on the device, or through a serviceannouncement. The UE may open a new PDN connection for those URLs thatcan be delivered on broadcast and Unicast.

The BM-SC 612 acts as the DASH-proxy 1006, and obtains content (from theDASH server 1012) for broadcast representations. The function of theDASH-proxy 1006 may include handling BC content upon a unicast tobroadcast handoff trigger. The trigger may include receiving a messagefrom the P-GW 610/HARD 1010 indicating a high rate attach event for thecontent. The function of the P-GW 610/HARD 1010 may include redirectingthe UE to switch from UC reception to BC reception through a ProtocolConfiguration Options (PCO) message, or through a HTTP redirectionmessage. The redirection signaling may also include the association orrelationship between the unicast transmission and the MBMS transmission,such as the content URL and TMGI for the associated MBMS transmission.The UE may also use PCO to signal the UE's capability to the P-GW if theP-GW supports demand based eMBMS so that the HARD module 1010 mayperform high attach rate detection only on the UEs capable of detectingthe switch from UC to BC or BC to UC and being capable of switchingreception modes. The function of the UE may include upon receiving anindication/redirection from the P-GW 610, initiating a procedure forreceiving a service-announcement from the broadcast channel or servicediscovery procedure from the unicast channel. The UC to BC indicationmay speed up the transition from UC delivery to BC delivery. Thefrequency on which the UE is/was receiving the content via unicastchannel may not support the BC transmission so that the UE may need toperform a service announcement on the broadcast channel of the BCtransmission transmitted on another frequency. The unicast and broadcastservices may or may not use the same MPD (called unified MPD).

FIG. 11 is a sequence diagram illustrating activities by variouscomponents of a wireless communications system implementing orsupporting a demand-based multicast service, according to embodimentsimplementing a seamless transition from unicast to broadcast. At step1110, the BM-SC 612 may send signaling to the P-GW 610 to enable theHARD function to monitor for specific URL(s) that may have high demandto detect high demand URL(s), where a high demand URL is a URL beingrequested by a number of users that exceeds a threshold. Alternatively,specific URL(s) that need to be processed by the HARD module 1010 may bepreconfigured at the P-GW. For example, the P-GW may receive thespecific URL(s) from an operator or from the BM-SC 612, e.g., the P-GWreceives a URL of where a new download is available. The P-GW mayreceive another indication that gives a hint of the URL(s) that arelikely to have high demand so that not all URLs need to be examined. Forexample, the P-GW may receive a list of online sites offering news,traffic, movies, and other content so that the P-GW needs to processonly the URL(s) from the list of online sites offering the content. Inyet another alternative, the P-GW/HARD may perform deep packetinspection (DPI) for all flows. This DPI inspection may be performed ina traffic detection function (TDF) entity. At step 1112, an applicationat the UE 602 requests content found at a URL. The UE requests thecontent via unicast mode, at step 1113. At step 1114A, the UE sends arequest for the content by sending an http-GET including a unicast URLand UE location information, e.g., a Cell Global ID (CGI), to the P-GW610. Real-time transport protocol (RTP) control protocol (RTCP) messagesmay be used in addition to or in lieu of HTTP messages. For example, atstep 114A, the UE may alternatively or additionally send a request forthe content by sending an RTCP message including either or both a URLand UE location information. The CGI indicates the cell where the UE iscurrently located at. Other position location information may also beincluded such as, for example, MBSFN Area ID, tracking area ID, etc. Atstep 1114B, the http-GET is forwarded from the P-GW to the DASH server.At steps 1116A-B, the DASH server 1012 responds (step 1116A) to therequest with an http-REPLY message via the P-GW 610 (step 1116B) to theUE 602. At step 1118, the HARD module 1010 detects high demand forcontent by counting the number of UEs accessing the same content fromthe same area. The HARD module 1010 may check the URL(s) on all outgoingpackets. Only the URLs of content/services that may be potentiallytransmitted over eMBMS may be counted. Further, only those UEs that havesubscription for eMBMS or enabled for demand based eMBMS reception maybe included in the High Attach Rate detection process. For example, theP-GW may obtain eMBMS capability information, including subscriptioninformation for UEs, from a home subscriber server (HSS), or getinformation from the UE via a PCO message during the PDN connectionestablishment. UE location information may be obtained through thefollowing methods: 1) having the UE include CGI information in theHTTP-GET message; 2) having the UE include location information in anRTCP message; 3) retrieving the location information via a NetworkProvided Location Information (NetLoc) service (as described in 3GPP TR23.842), which is a CGI-based method added in Rel-11; or 4) existingmeans such as counting, MBMS user service registration, secure userplane location (SUPL), etc. At step 1120, the HARD module 1010 mayinform the DASH-proxy 1006 when the number of users accessing a servicefrom an area crosses a pre-defined threshold. Threshold hysteresis maybe configured to prevent ping-ponging between set up and tear down ofthe eMBMS session. The threshold values may be set based on a number ofactive users, number of cells, and/or a hysteresis range. For example,the number of UEs in an area may exceed a first threshold T1, and thendelivery of the content is switched from UC delivery to BC delivery.Then, the number of UEs in the area may drop to less than a secondthreshold T2, where delivery of the content is switched from BC deliveryto UC delivery. The first threshold T1 may be greater than the secondthreshold T2. For example, the first threshold T1 may be defined as 100,with T2 defined as 70 for a hysteresis range (T1-T2) of 30. At step1122, based on the received number of users crossing the pre-definedthreshold, the DASH-proxy 1006 may decide to establish an eMBMS session.Steps 1124 through 1134 illustrate signaling between the network andmobile components to establish the eMBMS session and broadcast thecontent. At step 1124, the eMBMS session setup is performed between theMME/eNB and the P-GW, and between the P-GW and BM-SC. After the eMBMSsession setup is performed, the MME/eNB sends an MCCH update to the UEat step 1126. At step 1128, a service announce message is broadcast tothe UE 602. Optionally in a ‘pull’ configuration, at step 1130, theBM-SC 612 may send an http-GET message to the DASH server for thebroadcast content to pull content from the DASH server. At step 1132,the DASH server sends an http-REPLY to the BM-SC 612/DASH-proxy 1006. Ifthe optional step 1130 is not performed, the DASH server may send thebroadcast content in a ‘push’ configuration without an initial requestfrom the BM-SC 612/DASH-proxy 1006. At step 1134, the content is sent ina broadcast transmission to the UE.

At step 1136, the BM-SC 612 may notify the HARD module 1010 to disableHARD functions when the MBMS session has been set up. The BM-SC 612 mayalso notify the P-GW 610 whether the UE 602 should not be served via theUC channel after a certain time. At step 1142, the P-GW 610 thennotifies the UE 602 to switch from receiving content via UC transmissionto receiving content via BC transmission. The switch in reception modemay be performed via signaling such as, for example, PCO or HTTPredirection. For single frequency deployment, the P-GW 610 may not needto notify the UE 602 to make the switch. For multiband, multi-frequencydeployment, the signaling may trigger the UE to read overhead messagesto determine on which frequency to tune to receive the service over BCmode. The UE may obtain frequency information from a SIB and/or a USD,or from switching redirection signaling received from the P-GW. Themethod may follow a Make before Break model where BC transmission isstarted before stopping UC transmission. In the Make before Break model,the DASH-proxy/BM SC 612, 1006 may start the eMBMS session, and once theBC transmission is started, then the HARD module 1010 may stop detectionof URLs. The UE 602 may continue reception via the UC mode until it isready to receive the service via the MBMS session. Then the unicastchannel may be torn down; or the eNB may tear down the unicast channelbased on detection of no data activities over the unicast channel for aconfigurable time period. If the UE continues to use the unicast channelto get service after the P-GW indicates a switch to BC mode, after thegrace period, the P-GW may need to perform enforcement to make sure theUE is no longer using the unicast channel. The P-GW may trigger theresource release by releasing the PDN connection or the P-GW may dropthe HTTP-GET received from the UE and not forward the HTTP-GET to theDASH server.

FIG. 12 is a sequence diagram illustrating activities by variouscomponents of a wireless communications system implementing orsupporting a demand-based multicast service, according to embodimentsimplementing seamless transition from broadcast to unicast. The functionof the BM-SC 612/DASH-proxy 1006 may include deciding whether to switchto unicast based on MBMS counting. The BM-SC 612/DASH-proxy 1006 maymake an indication to the UEs through in-band Schedule Fragmentinformation or via a file delivery table (FDT) on a URL whoserepresentation signals a BC to UC transition. The function of the UE 602may include, upon receiving the in-band Schedule Information Fragment orthe indication from the FDT, (1) continuing to receive the content fromthe BC channel, or (2) initiating unicast channel establishment. If thein-band Schedule Information Fragment is used at step 1220, the UE knowsthe BC transmission end time from the Schedule Information. Before BCtransmission ends, the DASH client may start to query for DASH segmentsthrough the unicast transmission based on the MPD representation period.Alternatively, the MPD may use a BaseURL@serviceLocation to indicate aBC-to-UC-transition. The DASH segments identified by the URLs that arerepresented with a BC-to-UC transition are obtained through thebroadcast channel. Both unicast and broadcast transmissions of thecontent may use the same MPD, which lists all URLs used for unicast andbroadcast transmission.

Switching from broadcast delivery to unicast delivery may not cause aservice interruption because the network may continue to deliver thecontent using eMBMS for a period of time to allow the UEs to switch toUC reception. To establish the broadcast to unicast handoff, the networkmay need to determine (e.g., count) how many users are interested in acertain broadcast service from a particular area. The procedure may useRAN-based counting as defined in the standards, or the procedure may bebased on registration information. When the RAN (e.g., MCE) detects thenumber of UEs that are interested in a MBMS service is below apreconfigured threshold, the MCE may inform the BM-SC that the number ofUEs interested in the service is below the threshold. Next, in a Makebefore Handoff procedure, the DASH-proxy 1006 may set up unicastdelivery prior to stopping broadcast delivery or the UE may set upunicast reception prior to stopping broadcast reception to preventservice disruption as long as the UE switches to UC reception before theBC transmission end time. For example, in one aspect, the DASH-proxy1006 may send in-band scheduling information to indicate a BCtransmission end time. In another aspect, DASH-proxy 1006 may startusing the representation (using FDT in FLUTE) that indicates ‘broadcastto unicast transition’. In yet another aspect, DASH-proxy 1006 maycontinue with the MBMS session but indicate to the UE to transition toUC via FDT. If the in-band scheduling information is used for indicatinga BC transmission end time, the DASH client may continue to query forthe DASH segments through unicast based on the MPD representation periodafter the BC transmission ends. When the UE 602 obtains the URL whoserepresentation signals a BC to UC transition (e.g., a ‘broadcast tounicast transition’ message) or receives the indication of the signal totransition from BC to UC from the FDT, the UE 602 may initiate aprocedure to setup the unicast channel. The BM-SC 612 may indicate tothe P-GW to start the HARD function upon making the decision to switchfrom BC to UC.

FIG. 13 is another block diagram illustrating components of anotherwireless communication system for providing or supporting a demand basedtransition of content delivery between MBMS and unicast service. TheHARD module 1010 may be co-located with the BM-SC 612. The HARD module1010 may count the number of UEs accessing the same service from thesame area. The DASH-proxy 1006 may be co-located with the BM-SC 612 orwith the CDN, or may function as a separate entity. The DASH-proxy 1006may act as the ‘hub’ for both UC & BC data paths and may act as theunicast socket-connection endpoint setup by the UE 602. Further, theDASH-proxy 1006 may obtain an MPD from the DASH server and send it to UE602 (either through service announcement or service discovery or unicastMPD download). The DASH-proxy 1006 may interact with the BM-SC 612 tosend demand-based services on eMBMS. The BM-SC 612 may act as a DASHclient (now shown), and obtain content (from the DASH server 1012) forthe broadcast representations.

FIG. 14 is a sequence diagram illustrating activities by variouscomponents of another wireless communications system implementing orsupporting a demand-based multicast service, according to embodimentsimplementing a transition from unicast to broadcast. The function of theDASH-proxy 1006 may include, in the unicast mode, forwarding thehttp-GET request (step 1414C) to the DASH server 1012, and forwardingthe response (step 1416C) from DASH server 1012 back to the UE 602. Uponreceiving a UC to BC handoff trigger, the DASH-proxy 1006 may startredirecting http GET requests for a UC-URL to a URL whose representationsignals a UC to BC transition. The function of the UE 602 may include,upon receiving a redirection, the following: 1) getting the content fromthe re-directed URL; and 2) initiating a procedure for receiving aservice-announcement. Using a URL representation to signal the UC to BCtransition in the HTTP redirect may speed up the transition from UCdelivery to BC delivery. Also, the UC frequency may not support BC sothat the UE 602 may need to receive the service announcement on anotherfrequency. The MPD may use BaseURL@serviceLocation to indicate aUC-to-BC-transition. The DASH segments identified by the URLs that arerepresented with a UC-to-BC transition are obtained through the unicastchannel. Both unicast and broadcast transmissions may use the same MPD.In another implementation, the UC to BC transition may be indicatedthrough a new field added to the http REPLY message or using an httpreject message with a new error code to indicate that the UE shouldswitch from UC to BC. If, after the grace period, the UE continues touse the unicast channel to get service after the DASH-proxy redirectsthe UE to BC mode, the DASH-proxy/BM-SC/HARD may need to performenforcement to make sure the UE is no longer using the unicast channel.The DASH-proxy/BM-SC/HARD may drop the HTTP-GET received from the UE andnot forward the HTTP-GET to the DASH server.

At steps 1414A-B, the P-GW may redirect http-GET requests from the UE tothe DASH-proxy using the following alternatives: alternative 1) the UE602 may be provided with the BM-SC 612/DASH-proxy 1006 address throughthe MPD for the content that may be switched to eMBMS; alternative 2)use a special access point name (APN) (e.g., a dedicated AP). At step1418, the HARD module 1010 located in the BM-SC 612 detects high demandfor content by counting the number of UEs accessing the same contentfrom the same area. Then the HARD module 1010 may check URL(s) on alloutgoing packets. UE location information may be obtained: 1) by havingthe UE include CGI information in the HTTP-GET message; 2) having the UEinclude location information in an RTCP message; 3) retrieving thelocation information via a Network Provided Location Information(NetLoc) service (as described in 3GPP TR 23.842), which is a CGI-basedmethod added in Rel-11; or 4) via existing means such as accounting,MBMS user service registration, SUPL, etc. At step 1420, when the numberof users accessing the service from an area crosses a pre-definedthreshold, the BM-SC 612 may determine to switch delivery of content toan eMBMS session. Threshold hysteresis may be configured to preventping-ponging between set up and tear down of the eMBMS session. Forexample, the number of UEs in an area may exceed a first threshold T1,and then delivery of the content is switched from UC delivery to BCdelivery. Then, the number of UEs in the area may drop to less than asecond threshold T2, where delivery of the content is switched from BCdelivery to UC delivery. The first threshold T1 may be greater than thesecond threshold T2.

FIG. 15 is a sequence diagram illustrating activities by variouscomponents of another wireless communications system implementing orsupporting a demand-based multicast service, according to embodimentsimplementing a seamless transition from broadcast to unicast. Thefunction of the BM-SC 612/DASH-proxy 1006 may include deciding whetherto switch to unicast delivery based on counting. The BM-SC612/DASH-proxy 1006 may make an indication to the UEs via a FDT with aURL whose representation signals a BC to UC transition. The function ofthe UE 602 may include, upon receiving the indication in the FDT, (1)continuing to receive the content from the BC channel, or (2) initiatingunicast channel establishment. At step 1520, the MPD may use aBaseURL@serviceLocation to indicate a BC-to-UC-transition. The DASHsegments identified by the URLs containing a BC-to-UC transitionindication are obtained through the broadcast channel. Both unicast andbroadcast transmissions of the content may use the same MPD. During abroadcast to unicast delivery switch, the network may continue todeliver the requested content using eMBMS for a period of time to allowthe UEs switch to the unicast reception. To establish the broadcast tounicast handoff, the network may need to determine (e.g., count) howmany users are interested in a certain broadcast service in a particulararea. The procedure may use RAN-based counting as defined in thestandards, or the procedure may be based on registration information.When the RAN (e.g., the MCE) detects that the number of UEs interestedin a MBMS service is below than a preconfigured threshold, the MCE mayinform the BM-SC that the number of UEs interested in the service isbelow the threshold. Next, in a Make before Handoff procedure, theDASH-proxy 1006 may send in-band scheduling information to indicate a BCtransmission end time. The DASH-proxy 1006 may start using therepresentation (e.g., an indication using FDT in FLUTE) that indicates‘broadcast to unicast transition’, or the DASH-proxy 1006 may continuewith the MBMS session but indicate to the UE via the FDT to transitionto UC delivery, for example, by including a transition flag in the FDT.If in-band scheduling information is used for indicating a BCtransmission end time, the DASH client may query for the DASH segmentsthrough unicast based on the MPD representation period after thebroadcast transmission ends. When the UE 602 obtains the URL containinga ‘broadcast to unicast transition’ message or receives an indication(such as the transition flag) in the FDT, the UE 602 may initiate aprocedure to setup the unicast channel. The BM-SC 612 may activate theHARD function upon making the decision to switch from BC to UCtransmissions.

FIG. 16 shows a table 1600 illustrating a comparison between the methodsillustrated in FIG. 10 (Option 1) and FIG. 13 (Option 2).

FIG. 17 is a block diagram illustrating components of another wirelesscommunication system for providing or supporting seamless transitionbetween MBMS and unicast service based on demand for a content. The HARDmodule 1010 may be co-located with the content provider, for example,DASH server 1012. The UE 602 may download content from the DASH server1012 using a unicast channel. For example, the UE may download contentthrough the unicast bearer 1710 via the P-GW 610, as illustrated in path1712. The HARD module 1010 at the DASH server 1012 may detect a highdemand based on a high count of UEs accessing a same content (“highinterest” content). Based on the detected demand, the HARD module 1010may inform the DASH server 1012 or BM-SC 1006 to transition delivery ofthe content from unicast to broadcast transmission and initiate an eMBMSflow. The HARD module 1010 may inform the DASH server 1012 of theavailability of the broadcast transmission upon turning on the eMBMSflow, e.g., as illustrated in path 1720. Content may be sent to the UE602 from the Dash server 1012 via the BM-SC through path 1732. The BM-SC1006 may act as a DASH client and obtain, via path 1732A, 1) the MPDfrom the DASH server 1012 for transmission to the UE 602, and 2) thecontent for all representations that are used for transmission of thecontent over the eMBMS. The BM-SC 1006 may send the MPD and the contentto the UE 602, e.g., via the eMBMS bearer 1730, via path 1732B. The MPDmay be sent using a service announcement, and the content may be sentusing the representation chosen for the MBSFN.

FIG. 18 is a block diagram illustrating components of yet anotherwireless communication system for providing or supporting transitionbetween MBMS and unicast content delivery based on demand for a content.In FIG. 18, the HARD module 1010 may be a separate module or astand-alone module. The HARD module 1010 may be located at a differentphysical location than the, e.g., P-GW 610 or DASH server 1012. Forexample, the HARD can be co-located with an edge cache. A communicationtunnel 1810 may connect the P-GW 610 and the HARD module 1010. Datapackets may be sent between the P-GW 610 and HARD module 1010 via thetunnel 1810. The UE 602 downloads content from the DASH server 1012using unicast transmission, e.g., via the path 1820. For example, theBM-SC may act as a proxy for the DASH server 1012 when transmittingcontent to the UE 602 via the P-GW 610, e.g., via path 1820 through theHARD module 1010 and path 1810. The HARD module 1010 may detect a highdemand based on a high count of UEs accessing a same content (“highinterest” content). Based on the detected demand, the HARD module 1010may inform the BM-SC 1006 to transition to delivery of the content viabroadcast transmission and initiate an eMBMS flow. The BM-SC 1006 mayact as a DASH-proxy and obtain, e.g., via path 1830A, 1) the MPD fromthe DASH server 1012 for transmission to the UE 602, and 2) the contentfor all representations that are used for transmission over the eMBMS.The BM-SC 1006 may send the MPD and the content to the UE 602, e.g., viapath 1830B. The MPD may be sent using a service announcement, and thecontent may be sent using the representation chosen for the MBSFN.

FIG. 19 is a another block diagram illustrating components of a wirelesscommunication system for providing or supporting seamless transitionbetween MBMS and unicast service based on a demand for a content. In theembodiment of FIG. 19, a simplified HARD (S-HARD) module 1910 andDASH-proxy 1006 are co-located with the BM-SC 612. The S-HARD module1910 is “simplified” as it may be located in a control plane rather thana user plane. In the user plane configuration (e.g., the embodimentillustrated in FIG. 10), the HARD module 1010 may be co-located with anetwork entity receiving requests for unicast content from UEs. The HARDmodule 1010, in the user plane configuration, may determine demand for acontent by processing the received requests for the content. In thecontrol plane configuration, the S-HARD module 1910 may not beco-located with a network entity receiving requests for unicast contentfrom UEs. The S-HARD module 1910 may be co-located with a network entityoutside of the transmission path for requests for unicast content fromUEs. The UEs may include logic or programming to report reception ofunicast services to the S-HARD module 1910. At the S-HARD module 1910, acount of the UEs accessing a same service from a same area may bedetermined to detect high interest so that the delivery of the contentmay be transitioned to transmission from UC to BC.

A seamless transition is a transition of delivery of content to a mobiledevice, such as UE 602, from UC to BC or BC to UC without or withminimal service interruption. The content provider/internet serviceprovider (ISP) 614 may include a DASH server 1012. The system mayinclude a unicast DASH path 1020 for transmission of the DASH segmentsfrom the content provider/(ISP) 614 to the DASH client 1002 in the UE602 via the P-GW 610. Between the content provider/ISP 614 and BM-SC612, either a unicast path or the multicast path can be used. The systemmay include a broadcast DASH path 1024 for transmission of the DASHsegments from the DASH-proxy 1006 in the BM-SC 612 to the Broadcastservice layer 1004 in the UE 602 via the MBMS-GW 616 and the eNB 604.The system may include a unicast DASH path (not shown). For example, theUE 602 may download content from the DASH server 1012 using unicast whenthe BM-SC 612 acts as a proxy for the DASH server. The BM-SC 612 maytransmit data via the P-GW (connection not shown). A broadcast sessionmanagement connection 1022 is shown as a dashed line between the BM-SC612, MBMS-GW 616, MCE 606, MME 608, and eNB 604. A unicast sessionmanagement connection 1912 is shown in dashed line between the UE 602and BM-SC 612 through eNB 604 and P-GW 610. A broadcast service layerinterface 1026 is shown between the broadcast service layer 1004 andDASH client 1002. The wireless communication system may include theS-HARD module 1910. The S-HARD module 1910 may be co-located with theBM-SC 612. For example, The S-HARD module 1910 may receive reports fromUEs that receive services through the unicast channel. The S-HARD module1910 may count the number of UEs accessing the same service or contentvia a unicast transmission from the same area to determine an aggregatedemand. When the S-HARD module 1910 detects a high count of UEsaccessing the same service/content (“high interest”), the S-HARD module1910 may inform the DASH-proxy 1006. Thereafter, the DASH-proxy 1006 mayinteract with the BM-SC 612 to notify the UE 602 once a broadcastservice is available or when the content is switched from unicastdelivery to broadcast delivery.

The DASH-proxy 1006 may be co-located with the BM-SC 612, a contentdelivery network (CDN), or as a separate entity. Acting as the ‘hub’,the DASH-proxy 1006 serves only the broadcast data path. The DASH-proxy1006 may inform the S-HARD module 1910 when the BC mode is started. TheDASH-proxy 1006 may obtain a media presentation description (MPD) fromthe DASH server 1012 and send it to the UE 602 (either through a serviceannouncement, service discovery, or unicast MPD download). TheDASH-proxy 1006 may interact with the BM-SC 612 to send the demand-basedservice on eMBMS. The BM-SC 612 may signal the UE 602 to switch fromreception of content via unicast delivery to reception of the contentvia broadcast delivery.

The DASH-proxy 1006 within the BM-SC 612 (or the BM-SC acting as aDASH-proxy 1006), and obtains content (from the DASH server 1012) forbroadcast representations. The function of the DASH-proxy 1006 mayinclude handling BC content upon a unicast to broadcast handoff trigger.The trigger may include receiving a message from the S-HARD module 1910indicating a high rate attach event for the content. The function of theBM-SC 612 may include signaling the UE to switch from UC reception to BCreception of the content.

FIG. 20 is a sequence diagram illustrating activities by variouscomponents of a wireless communication system implementing or supportinga demand-based multicast service, in accordance with the embodiment ofFIG. 19. The S-HARD module 1910 is located in the control plane, and theUE 602 may need to report received content to the S-HARD module 1910 atthe BM-SC 612. To report received content, the UE 602 may need to obtainthe BM-SC 612 location. The UE 602 may be pre-configured with the BM-SC612 address (for example, IP address). The UE 602 may obtain the BM-SC612 address through a unicast MPD, service discovery, serviceannouncement, or MPD data included in USD. The UE 602 may send a reportto the BM-SC 612 when the UE 602 starts to receive the content which isdesignated in the reporting list, when the UE changes location whilereceiving the content, or when the UE finishes or stops receiving thecontent. The report may include a URL of the content or MPD, a locationof the UE (e.g., CGI/MBSFN AreaID), or start and stop indications.

At step 2010, the UE 602 may obtain a list of content to report and anetwork destination for the report. The network destination may includethe BM-SC 612 location, such the BM-SC 612 server IP address. At step2012, an application at the UE 602 requests content specified by a URL.The UE 602 requests the content via unicast mode, at step 2014. At step2016A, the UE 602 requests the content by sending an http-GET includinga unicast URL with UE location information such as, e.g., CGIinformation, to the P-GW 610. The CGI indicates the serving cell of theUE 602. Other position location information may be included. Thehttp-GET is forwarded from the P-GW 610 to the DASH server 1012, at step2016B. At steps 2018A-B, the DASH server 1012 responds to the requestwith an http-REPLY message sent via the P-GW 610 to the UE 602. At step2020, the UE 602 may report the received service URL to the S-HARDmodule 1910 at the BM-SC 612. The report from the UE 602 may includelocation (for example, CGI, MBSFN Area ID, tracking area ID, etc.)information. The received service URL may be included in the list ofcontent to report. At step 2022, the S-HARD module 1910 may count anumber of UEs in a same area accessing some content and compare thecount to a threshold to detect high demand for the content. At step2024, the S-HARD module 1910 may inform the DASH-proxy 1006 when thenumber of users accessing a service from an area crosses a pre-definedthreshold. The DASH-proxy 1006 may determine to set up an eMBMS sessionbased on the information from the S-HARD module 1910. Thresholdhysteresis may be configured at the S-HARD module 1910 to preventping-ponging between set up and tear down of the eMBMS session. Thethreshold values for the threshold hysteresis may be set based on anumber of active users, number of cells, and/or a hysteresis range. Forexample, a first threshold T1 may be defined as 100, and a secondthreshold T2 defined as 70 for a hysteresis range (T1-T2) of 30. Forexample, the number of UEs in an area may exceed the first threshold T1,and then delivery of the content is switched from UC delivery to BCdelivery. Then, the number of UEs in the area may drop to less than thesecond threshold T2, where delivery of the content is switched from BCdelivery to UC delivery. The first threshold T1 may be greater than thesecond threshold T2. Steps 2026 through 2040 illustrate signalingbetween the network and mobile components to establish the eMBMS sessionand broadcast the content. At step 2026, based on the received number ofusers crossing the pre-defined threshold, the DASH-proxy 1006 may decideto establish an eMBMS session. The eMBMS session setup is performedbetween the MME/eNB 608, 604 and the BM-SC/DASH-proxy 612, 1006. Afterthe eMBMS session setup is performed, the MME/eNB 608, 604 sends an MCCHupdate to the UE 602 at step 2028. At step 2030, a service announcementmessage is broadcast to the UE 602. At step 2032, the DASH-proxy 1006sends a redirection message to signal the UE 602 to switch from UC toBC. The redirection message may optionally include an MBMS service key(MSK) to speed up transition from UC to BC. At step 2034, the UE 602 mayinitiate a service discovery procedure or service announcement procedureto obtain the broadcast MPD. Optionally in a ‘pull’ configuration, atstep 2036, the BM-SC 612 may send an http-GET message to the DASH server1012 for the broadcast content to pull content from the DASH server1012. At step 2038, the DASH server 1012 sends an http-REPLY to theBM-SC 612. If the optional step 2036 is not performed, the DASH server1012 may send the broadcast content in a ‘push’ configuration without aninitial request from the BM-SC 612. At step 2040, the UE 602 mayindicate to the eNB 604 the frequency on which the UE 602 desires toreceive the broadcast transmissions. At step 2042, the content is sentin BC mode, and the UE 602 receives the content via broadcasttransmissions. At step 2046, the unicast channel between the UE 602 andMME/eNB 608, 604 is torn down.

FIG. 21 is a sequence diagram illustrating activities by variouscomponents of a wireless communication system providing or supportingNetLoc location determination.

FIG. 22 is a sequence diagram illustrating activities by variouscomponents of a wireless communications system for a UE-based solution(which may also be referred to herein as a UE autonomous switch) forswitching from unicast reception of content to broadcast reception ofthe content when the unicast transmission and broadcast transmission areon the same frequency. Assuming the network uses implementationdependent solutions or uses the solutions specified above to detect highattach rate without sending redirection signaling to the UE to switchfrom the UC to BC, the following apply. Upon detection of a high attachrate event, the network decides to enable BC transmission. Then, thenetwork sets up an eMBMS session and updates the system informationblocks SIB2/SIB13 and the multicast control channel (MCCH). The networkupdates USD (USD is sent either on the broadcast channel or the unicastchannel based on a UE request on the unicast session). The following maybe used to trigger the UE 602 to perform SIB (e.g., SIB2/SIB13) and MCCHmonitoring, and to perform service discovery (via unicast) and serviceannouncement (via broadcast) procedures. First, the UE 602 mayperiodically perform the monitoring and service discovery procedures.For example, the UE 602 may be triggered to perform the monitoring andservice discovery procedures based on a predetermined schedule or timewindows. Second, the UE 602 may perform the monitoring and servicediscovery procedures based on detecting signal degradation of unicasttransmissions (for example, due to network congestion). Third, the UE602 may receive notifications from the network through applicationsignaling, such as SMS, OMA PUSH, USD, etc. to trigger the UE to performthe monitoring and service discovery procedures. Fourth, the UE mayreceive an indication of a unicast release or access barring of the UEfrom the RAN to trigger to UE to monitor and perform the serviceprocedures. Upon the UE acquiring the USD via service announcement anddiscovery procedures at step 2224, the UE determines that the TMGI(s) ofinterest are sent over broadcast channel. The UE then acquires the MCHScheduling Information (MSI) and receives MTCH which broadcasts thecontent of the corresponding TMGI. After the UE switches to BC mode, theunicast channel is torn down, or the eNB may tear down the unicastchannel based on detection of no data activities over the unicastchannel for a configurable time period.

FIG. 23 is a sequence diagram illustrating activities by variouscomponents of a wireless communications system for a UE-based solutionfor switching from unicast reception of content to broadcast receptionwhen the unicast transmission of the content and broadcast transmissionof the content are on different frequencies. If the UE determines thatthe broadcast service is sent on another frequency from the USD receivedfrom the BM-SC and from the SIB 15 received from the eNB, the UE sendsan MBMSInterestIndication to the eNB in step 5. The eNB then sends anRRC Connection Reconfiguration to the UE including mobility controlinformation to handoff the UE to another frequency (for example F2). TheUE then sends an RRC connectionReconfiguration to the eNB. If the UEcannot send MBMSInterestIndication to the eNB, for example, the eNB is apre-R11 eNB, the UE may drop the current UC connection and then tune tothe neighbor frequency (e.g., the new frequency). After handoff to thenew frequency, the UE may need to acquire SIB, MCCH, and MTCH forreceiving the content on the MBMS channel. After the UE enters BCreception mode, the unicast channel is torn down, or the eNB may teardown the unicast channel based on detection of no data activities overthe unicast channel for a configurable time period.

FIG. 24 is a sequence diagram illustrating activities by variouscomponents of a wireless communications system for a UE-based solutionfor switching from broadcast reception of the content to unicastreception of the content. A UE may buffer or cache sufficient contentprior to switching from one reception mode to another so that no serviceinterruption is perceived by the user of the UE. For example, the UE maybe receiving content from a multicast session before receiving thecontent from the multicast session is halted. The UE may furtherdetermine that 50 milliseconds are required to transition from themulticast session the unicast session, and that the UE may not be ableto receive content from the network during the transition. In this case,the UE may buffer 50 milliseconds of content before performing thetransition to the unicast session. During the transition, the UE maypresent the content from the buffer to the user so that the user doesnot perceive an interruption in the delivery of the content.

A UE-based approach for switching between UC to BC reception mode mayalso be used when the UE moves between UC only coverage and BC coveragedue to the UE's mobility. FIGS. 25 and 26 illustrate UC to BC and BC toUC switching call flows due to UE mobility.

FIG. 25 illustrates a call flow for switching from UC to BC receptionmode (as an example, DASH may be used for delivery of content via eitheror both UC and BC).

A description of each step may be as follows:

2512. The application requests a content. The UE 602 discovers it iswithin a UC only coverage area for content delivery. The UE 602 may sendan HTTP-GET message to the network. This step may use unicast DASHprocedures as specified in 3GPP TS 26.247.

2516A-B. The UE 602 may detect a new cell with BC delivery of thecontent, e.g., by receiving SIB messages from the new cell.

2518. The UE 602 may acquire a USD either via a unicast channel or abroadcast channel.

2520. If the UE 602 determines that the broadcast service is sent onanother frequency from the USD received from the BM-SC 612 and from theSIB 15 received from the eNB 604, the UE 602 may send anMBMSInterestIndication to the eNB 604.

2522. The eNB 640 may send an RRC Connection Reconfiguration to the UE602 including mobility control information to handoff the UE to anotherfrequency.

2524. The UE 602 may send an RRC connectionReconfiguration message tothe eNB 604.

2526. The UE 602 may acquire the SIB 13 including the MCCH radioconfiguration.

2528. The UE 602 may acquire an MBSFNAreaConfiguration message from theMCCH to obtain TMGI information.

2530. The UE 602 may determine that the TMGI of interest is sent over abroadcast channel.

2536. The UE 602 may acquire the MCH Scheduling Information (MSI).

2538. On the scheduled MBSFN subframes as indicated by MSI, the UE 602may receive the MTCH which broadcasts the content of the correspondingTMGI.

2540. The UE 602 may continue to receive the content from MBMS.

FIG. 26 illustrates a call flow for switching from BC to UC receptionmode.

A description of each step may be as follows:

2612A-E. The application requests a content. The UE 602 may determinethat it is within a MBMS coverage area. The UE 602 receives content viaMBMS.

2616. The UE 602 may detect that the MBMS coverage is weak or that theUE 602 has moved out of MBMS coverage (e.g., by moving into coverage ofa new cell). This may be done through one or more of the followingmethods:

-   -   by measuring MBSFN signal (e.g., MBSFN RSRP and RSRQ);    -   using information received in a SIB15; or    -   determining there is no SIB13 sent from the new cell.

2618. The UE 602 may establish a RRC connection with the eNB 604 (orcell).

2620. The UE 602 may establish a PDN connection if needed.

2622A-B. The UE 602 may send an HTTP-GET message to the network. Thisstep may use unicast DASH procedures as specified in 3GPP TS 26.247.

2624A-B. The DASH server 1012 may send an HTTP-REPLY to the UE 602through the P-GW 610. This step may use unicast DASH procedures asspecified in 3GPP TS 26.247.

If DASH is used for both UC delivery of a content and BC delivery of thecontent, a unified MPD may be used. The unified MPD may list all URLsused for unicast and broadcast transmission. If a RTP is used for bothUC delivery of content and BC delivery of content, the USD may list allURLs used for unicast and broadcast transmission of the content. The UE602 uses the information received from a MPD, and/or a USD, and/or a SIBto obtain the knowledge that the same content is available via UC and BCreception modes so that the UE 602 can switch between UC and BCreception.

It may also be the case that broadcast and unicast URLs for a contentare not the same. (The URL may be referencing either DASH MPD or an RTPstream). In such cases, a device may be able to predict a correspondingrelated unicast or broadcast URL via a known set of construction rules.For example, the construction rules may be rules processed at a mobiledevice. For example, the mobile device may determine the correspondingrelated unicast or broadcast URL based on a structural similaritybetween the unicast or broadcast URL and the corresponding relatedbroadcast or unicast URL, respectively. For example, the correspondingURLs may differ in a portion of the URL string such as, e.g., a prefix,suffix, etc. It is further possible that there are multiple possiblyvalid URLs within the given rules. The device may autonomously detectthe presence of a syntactically valid broadcast URL in the then currentUSD and elect to switch service to broadcast. Similarly, a devicedetecting loss or impending loss of broadcast service may requestpredicted unicast URLs, assuming that such behavior is allowed. Thisbehavior is not in lieu of requesting the currently defined unicast URLincluded in the currently valid USD, of a potentially or apparentlyfailing MBSFN signal, but in addition to the nominally expectedbehavior. For example, the device may perform the detection based onmobility of the device. For example, the device may be moving to anotherarea (e.g., another cell) and switch receiving content between unicastand broadcast. The device may autonomously switch receiving contentbetween unicast and broadcast in conjunction with or in response to cellreselection or handover. The device may have a predefined precedence(e.g., a priority ranking) with respect to order of unicast URLs toattempt, for example the currently defined unicast URL has highestpriority. It is possible that the network may have policies with respectto such behavior that the device must adhere to. (These policies may bedependent on the capabilities of the device for example a broadcastcapable device may take unicast, when broadcast is unavailable.) Thedevice may autonomously elect to switch to unicast, when such behavioris allowed and service conditions (QoS) dictate such a change or loss ofservice.

FIG. 27 illustrates a high-level MBMS and PSS architecture with variousmodes of content delivery. Content delivery to a UE 602 may originate atvarious sources. For example, the content may originate from theInternet 2790, an HTTP Server 2730, a packet switched streaming service(PSS) server 2740, and a BM-SC 612. The content may be delivered to theUE 602 via a PDN-GW 610, MBMS-GW 616, and/or the eNB 604. In oneexample, over-the-top (OTT) over UC content delivery may originate fromthe Internet 2790 and may be delivered via the PDN-GW 610 and eNB 604for delivery to the UE 602. In another example, PSS over UC mayoriginate from the PSS server 2740 or HTTP server 2730 and may bedelivered via the PDN-GW 610, or optionally originate from the contentprovider via the HTTP server 2730 or PSS server 2740, and the eNB 604for delivery to the UE 602. In another example, MBMS over UC mayoriginate from the PSS server 2740 or HTTP server 2730 and may bedelivered via the PDN-GW 610, or optionally originate from the contentprovider via the HTTP server 2730 or PSS server 2740, and the eNB 604for delivery to the UE 602. The MBMS over UC may be controlled by theBM-SC. In another example, MBMS over BC may originate from the BM-SC 612and may be delivered via the MBMS-GW 616 and eNB 604 for delivery to theUE 602.

A network operator may identify services that may be delivered viaeither BC or UC or both. The policy which can be preconfigured in anetwork entity (for example, PDN-GW, or HARD) or sent from anothernetwork entity (for example, a policy charging and rules function(PCRF), or BM-SC) may allow some content to be switched between UC andBC based on service URL(s) or other service identities. For example,only MBMS over UC can be allowed to switch between UC and BC; oroperator controlled PSS or HTTP service over UC is also allowed toswitch UC and BC; or non-operator controlled PSS or HTTP service over UCis also allowed to switch between UC and BC; or all services includingOTT over UC are allowed to switch between UC and BC. Additionally oralternatively, the server providing the content (e.g., the HTTP server,PSS server, BM-SC) may provide an indication to the network entity thatthe content may be delivered via UC, BC, or both. Delivery of thecontent may be switch between any of the content delivery methods. Forexample, the content may be switched from delivered via UC transmissionand BC transmission. For example, content delivered via the UCtransmission methods including over-the-top over UC, MBMS service overUC, and PSS over UC may be switched to BC transmission methods includingthe MBMS service over BC. For example, content delivered via the BCtransmission methods including MBMS service over BC may be switched toBC transmission methods including over-the-top over UC, MBMS serviceover UC, and PSS over UC.

FIG. 28 is a sequence diagram illustrating activities by variouscomponents of a wireless communications system for switching fromcontent delivery via UC mode to content delivery via BC mode. Thisfigure shows switching from non-MBMS services over UC (for example, OTTservice over UC, PSS or HTTP service over UC) to MBMS over BC, usingDASH as an example. In order to switch from a UC delivery mode to a LTEBC delivery mode, there may be a need to have the HARD 624 function inthe core network or in the content server. The HARD 624 function may becollocated with the P-GW, the TDF, or with other network entities. Whenthe HARD 624 function detects that demand for a content has a highattach rate (e.g., number of the UEs that are receiving a content fromthe same area exceeds a configurable threshold based on a networkoperator policy), the HARD 624 function may send an indication to theBM-SC 612 to turn on eMBMS transmission, and switch content deliveryfrom a unicast mode of delivery to an eMBMS mode of content delivery.

Similarly, in order to switch from a LTE BC mode of content delivery toa UC mode of content delivery, there may be a need to have a LTEbroadcast counting mechanism in the radio network. For example, thecurrent counting mechanism specified in 3GPP TS 36.331 or some enhancedcounting mechanism may be used. When the radio network detects demandfor the content has a low attach rate (e.g., number of UEs that arereceiving a content from the same area drops below a configurablethreshold based on the network operator policy), the radio networkindicates the counting result to the BM-SC 612 which may decide whetheror not to turn off the eMBMS mode of content delivery. If eMBMStransmission of the content is disabled, the UE 602 may continuereceiving the content through a UC delivery mode.

The manner in which the HARD 624 function detects a high attach rate maybe implementation dependent. Therefore, in the various call flows, theCore Network entity may be shown without being further distinguishedamong the P-GW, the HARD 624 function, and the BM-SC 612.

Returning to FIG. 28, illustrated is one aspect for switching fromnon-eMBMS UC content delivery to BC content delivery (DASH may be usedfor both UC and BC content delivery). At step 2810, the applicationsends a request for a content. At step 2822A-B, the UE 602 discoversthat the content requested by the application is not available throughLTE broadcast (eMBMS?). The UE 602 may send an HTTP-GET message to thenetwork. The HTTP-GET message may include the UE's 602 locationinformation including, for example, a CGI. The core network (P-GW, whichis not shown in the call flow) may forward the HTTP-GET message to theDASH server. The HARD 624 function may be located in the path of theuser traffic. Steps 2820-2824 may use unicast DASH procedures asspecified in 3GPP TS 26.247.

At steps 2824A-B, the DASH server 1012 may send an HTTP-REPLY message tothe UE 602 through the P-GW. This step may use unicast DASH proceduresas specified in 3GPP TS 26.247. At step 2826, the HARD 624 function maydetect that the content has a high attach rate, e.g., the number of theUEs receiving the content from the same area exceeds a configurablethreshold based on network operator policy. The HARD 624 function mayuse the location information received from the UE 602 or use NetLoc asspecified in 3GPP TR 23.842. In step 2828, the HARD 624 function mayindicate to the BM-SC 612 that the content has a high attach rate. Instep 2830, the BM-SC 612 may decide to enable eMBMS transmission. Atstep 2832, the core network may set up an eMBMS session as specified in3GPP TS 23.246. At step 2834, the eNB 604 may apply a radio resourceconfiguration and send updated SIB13 and SIB15 information if needed.The eNB 604 may also perform MCCH change notifications to inform UEs ofthe presence of the eMBMS service. At step 2836, the BM-SC 612 may sendan updated USD that includes a unified MPD if needed. A unified MPD mayinclude parameters for all eMBMS services. At step 2838, the BM-SC 612may inform the P-GW/HARD to redirect the UE 602 from UC to BC receptionmode. At step 2840, the UE 602 may continue to use unicast DASHprocedures by sending an HTTP-GET message. At step 2842, once the MBMSsession has been established, the core network may send an HTTP-REDIRECTmessage to redirect the UE 602 to switch from UC to BC reception mode.At step 2844, upon receiving redirection from the network, the UE 602may initiate service discovery procedures to receive the USD through abroadcast channel if available or through a unicast channel if the USDis not available via the broadcast channel. At step 2846, if the UE 602has not registered with the MBMS service and the USD indicates thatregistration is required, the UE may perform MBMS service registrationand obtain a service key if service protection is enabled. At step 2848,based on the information received from the SIB15 message received overthe air and the USD received from the BM-SC 612, if the correspondingMBMS service is transmitted on a different frequency, the UE 602 maysend an MBMSInterestMessage to indicate the frequency of interest. Atstep 2850, the core network continues to send the HTTP-GET message tothe DASH server. At step 2852, the DASH server may reply with anHTTP-REPLY message. At step 2854, the BM-SC 612 sends the content viaDASH over MBMS. At step 2856, the UE 602 may receive DASH segments overthe corresponding MBMS channel and enter a BC mode of reception. Whenthe DASH client continues to request DASH segments, the MBMS client mayindicate to the DASH Client that the MPD should be updated. Furthermore,the DASH client may be redirected to, and eventually acquire the contentSegments from, the local server associated with MBMS reception.

FIG. 29 illustrates an aspect for switching from content delivery viaMBMS over UC to content delivery via MBMS over BC, using DASH as anexample.

A description of each step may be as follows:

2910. The application sends a request for a content.

2920. Since the service is a MBMS service, the UE 602 performs MBMSservice registration and obtains a service key if service protection isenabled.

2930. The UE 602 may acquire the USD with a unified MPD included viaeither a unicast channel or a broadcast channel.

2932A-B. The UE 602 may discover that the content requested by theapplication is not available through LTE broadcast (e.g., eMBMS). The UE602 may send an HTTP-GET message to the network. The HTTP-GET messagemay include the UE's 602 location information including, for example, aCGI. The core network (P-GW, which is not shown in the call flow) mayforward the HTTP-GET message to the DASH server. The HARD 624 functionmay be in the path of user traffic. This step may use unicast DASHprocedures as specified in 3GPP TS 26.247.

2934A-B. The DASH may server send an HTTP-REPLY message back to the UE602 through the P-GW. This step may use unicast DASH procedures asspecified in 3GPP TS 26.247.

2936. The HARD 624 function may detect that the content has a highattach rate, e.g., the number of the UEs that are receiving the contentfrom the same area exceeds a configurable threshold based on networkoperator policy. The HARD 624 function may use the location informationreceived from the UE 602 or may use NetLoc as specified in 3GPP TR23.842. The HARD 624 function may then send an indication to the BM-SCthat the content has a high attach rate. Alternatively, a MBMS countingmechanism specified in 3GPP TS 36.300 may be used. For example, when theMCE 606 detects a number of UEs that are interested in a TMGI exceeds apreconfigured threshold, the MCE 606 sends an indication to the BM-SC612.

2938. The BM-SC 612 may decide to enable eMBMS transmission.

2940. The core network may set up an eMBMS session as specified in 3GPPTS 23.246.

2942. The eNB 604 may apply radio resource configuration and sendupdated SIB13 and SIB15 if needed. The eNB 604 may also perform MCCHchange notifications to inform UEs of the presence of eMBMS service.

2944. The BM-SC 612 may send an indication to the P-GW/HARD or HTTPserver/PSS server to redirect the UE 602 from UC to BC reception mode.

2946A-B. The UE 602 may continue to perform unicast DASH procedures bysending an HTTP-GET message.

2948A-B. Once the MBMS session has been established, the core networkmay send an HTTP-REDIRECT message to redirect the UE 602 from UC to BCreception mode.

2950. Based on the information received from SIB 15 over the air and USDfrom BM-SC 612, if the corresponding MBMS service is transmitted on adifferent frequency, the UE 602 may send an MBMSInterestMessage toindicate the frequency of interest.

2952. The core network may continue to send an HTTP-GET message to theDASH server.

2954. The DASH server may reply with an HTTP-REPLY message.

2956. The BM-SC 612 may send the content via DASH over MBMS.

2958. The UE 602 may receive DASH segments over an MBMS channel andenter a BC reception mode. The DASH client may continue to send requestsfor DASH segments. If so, the MBMS client may send an indication to theDASH Client that the MPD should be updated. Furthermore, the DASH clientmay be redirected to, and eventually acquire the Segments from, thelocal server associated with MBMS reception.

FIG. 30 illustrates an aspect for switching a UE from content deliveryvia MBMS over BC to content delivery via a UC reception mode (DASH maybe used for both UC and BC delivery of the content).

A description of each step may be as follows:

3010A-D. An application is on (in a running state), and DASH over MBMSis on-going. The UE 602 is in BC reception mode.

3012. The eNB 604/MCE 606 communicates with the BM-SC 612 to report acounting result for a content being transmitted via BC delivery ofcontent.

3014. The BM-SC 612 may decide to switch from a BC to a UC contentdelivery mode based on the MCE's 606 input or based on other information(for example, expiration of a preconfigured timer or MBMS registrationinformation).

3016. The BM-SC 612 may use an in-band Schedule Fragment Information toindicate the end of MBMs transmission of the content. For example, theSchedule Fragment Information may be sent within the eMBMS transmission.

3018. The UE 602 may obtain the in-band Schedule Fragment Informationand detect that the MBMS session is about to end.

3020. The UE 602 may establish an RRC connection prior to the MBMSsession end time.

3022. The UE 602 may also establish a PDN connection if needed.

3024A-B. The BM-SC 612 may perform MBMS session stop procedures asspecified in 3GPP TS 23.246.

3026. The UE 602 may enter a UC reception mode.

3028-3030. The UE 602 may continue to use unicast DASH procedures toreceive content by sending HTTP-GET messages.

FIG. 31 illustrates an aspect for switching from content reception vianon-eMBMS UC to content reception via BC, where an RTP may be used fordelivery of content via UC and delivery of content via BC.

A description of each step may be as follows:

3110. The application sends a request for a content.

3120. The UE 602 may discover that the content requested by theapplication is not available through LTE BC. The UE may send SIPsignaling to set up an RTP session. The SIP message may include the UE's602 location information including, for example, CGI.

3122. An RTP streaming and RTCP may be established between the UE 602and the RTP Server 3930.

3124. The HARD 624 function, which may be located in the path of SIPsignaling or the RTP user traffic path, detects a content with a highattach rate, e.g., the number of the UEs receiving the content from thesame area exceeds a configurable threshold based on network operatorpolicy. The HARD 624 function may send an indication of the high attachrate content to the BM-SC 612.

3126. The BM-SC 612 may decide to enable eMBMS transmission.

3128. The BM-SC 612 may set up an eMBMS session as specified in 3GPP TS23.246.

3130. The eNB 604 may apply radio resource configuration and sendupdated SIB13 and SIB15 information if needed. The eNB 604 may alsoperform MCCH change notifications to inform UEs of the presence of theeMBMS service.

3132. The BM-SC 612 may send an updated USD which includes a unified MPDif needed.

3134. Once the MBMS session has been established, the BM-SC 612 mayindicate to the RTP server to redirect UE 602 from UC to BC receptionmode.

3136. The RTP server may redirect the UE 602 to switch from a UC to a BCreception mode using RTCP messages.

3138. Upon receiving redirection from the network, the UE 602 mayinitiate service discovery procedures to receive the USD through abroadcast channel if available or through a unicast channel if the USDis not available from the broadcast channel.

3140. If the UE 602 has not registered for the MBMS service and the USDindicates that registration is required, the UE 602 may perform MBMSservice registration and obtain a service key if service protection isenabled.

3142. Based on the information received from SIB 15 over the air and theUSD received from the BM-SC 612, if the corresponding MBMS service istransmitted in a different frequency, the UE 602 may send anMBMSInterestMessage to indicate the interested frequency.

3144. The BM-SC 612 may request RTP packets from the RTP server.

3146. The RTP server sends the RTP packets to the BM-SC 612.

3148. The BM-SC 612 may send the content to the UE 602 via RTP streamingover MBMS.

3150. The UE 602 receives RTP packets over the MBMS channel and entersBC reception mode.

FIG. 32 illustrates an aspect for switching from MBMS over UC to BCdelivery mode, where RTP may be used for delivery of content via UC anddelivery of content via BC.

A description of each step may be as follows:

3210. The application requests a content.

3212. Since the service may be an MBMS service, the UE 602 may performMBMS service registration and may obtain a service key if serviceprotection is enabled.

3214. The UE 602 may acquire a USD with a unified MPD included viaeither a unicast channel or a broadcast channel.

3216. The UE 602 may discover that the content requested by theapplication is not available through LTE broadcast. The UE 602 may sendSIP signaling to establish a RTP session. The SIP message may includethe UE's location information, for example CGI.

3218. RTP streaming and RTCP may be ongoing.

3220. The HARD 624 function, which may be in the path of SIP signalingor the RTP user traffic path, detects a content with a high attach rate,e.g., number of the UEs that are receiving the content from the samearea exceeds a configurable threshold based on network operator policy.The HARD 624 function may indicate such high attach rate content to theBM-SC 612.

3222. The BM-SC 612 may decide to enable eMBMS transmission of the highattach rate content.

3224. The BM-SC 612 may establish an eMBMS session to deliver thecontent as specified in 3GPP TS 23.246.

3226. The eNB 604 may use RRC control signals to send updated SIB13 andSIB 15 if needed. The eNB 604 may also perform MCCH change notificationsto inform UEs of the presence of eMBMS service.

3228. Once an MBMS session has been established, the BM-SC 612 may sendan indication to the RTP server to redirect the UE 602 from UC to BC.

3230. The RTP server may redirect the UE 602 to switch from UC to BCreception mode using RTCP messages.

3232. Based on the information received from SIB 15 over the air and USDfrom the BM-SC 612, if the corresponding MBMS service is transmitted ona different frequency, the UE 602 may send an MBMSInterestMessage toindicate the frequency of interest.

3234. The BM-SC 612 may request RTP packets from the RTP server.

3236-3238. The RTP server may send RTP packets to the BM-SC 612. TheBM-SC 612 may send the content via RTP streaming over MBMS.

3242. The UE 602 may receive the RTP packets over the corresponding MBMSchannel and may enter BC reception mode.

FIG. 33 illustrates switching from delivery of content via BC todelivery of content via UC, where RTP may be used in both delivery ofcontent via UC and delivery of content via BC.

A descriptions of each step may be as follows:

3310-3312. An application may be running on a UE 602 and delivery ofcontent via RTP over MBMS is on-going. The UE 602 is in BC receptionmode.

3314. The eNB 604/MCE 606 may communicate with the BM-SC 612 to report acounting result for content.

3316. The BM-SC 612 may decide to switch from BC to UC delivery modebased on the MCE's 606 input or based on other information (for example,expiration of a preconfigured timer or MBMS registration information).

3318. The BM-SC 612 may use an in-band Schedule Fragment Info toindicate the end of MBMS transmission of the content.

3320. The UE 602 may obtain the in-band Schedule Fragment Info anddetect that the MBMS session for the content is about to end.

3322. The UE 602 may establish an RRC connection before the MBMS sessionend time.

3324. The UE 602 may also establish a PDN connection if needed, e.g., ifa PDN used for MBMS has not been set up.

3326A-B. The BM-SC 612 may perform MBMS session stop procedures e.g., asspecified in 3GPP TS 23.246.

3328. The UE 602 may enter UC reception mode.

3330. The UE 602 may establish a RTP session via SIP signaling.

3332. The UE 602 may receive content via RTP packets over a unicastchannel.

In accordance with one or more aspects of the embodiments describedherein, with reference to FIG. 34A, there is shown a methodology 3400,operable by an apparatus, such as for example, a P-GW or a BM-SCincluding a HARD module. The method is not limited to performance by theP-GW or BM-SC and/or HARD module, and may be performed by any networkentity or combination of entities for which the defined operations arepossible and/or permitted by applicable standards. The method 3400 mayinclude, at 3402, determining whether an aggregate demand for a contentprovided via dedicated unicast transmissions exceeds a threshold. Themethod 3400 may further include, at 3404, switching transmission of thecontent from the dedicated unicast transmissions to a multicasttransmission upon a determination that the aggregate demand exceeds thethreshold.

With reference to FIG. 34B, there are shown further optional operationsor aspects of the method 3400. If the method 3400 includes at least oneblock of FIG. 34B, then the method 3400 may terminate after the at leastone block, without including any subsequent downstream block(s). It isfurther noted that numbers of the blocks do not imply a particular orderin which the blocks may be performed according to the method 3400. Forexample, the method 3400 may further include determining a count ofmobile entities in an area of the WCS (block 3406), receiving locationinformation of the mobile entities (block 3408), providing the contentvia multicast transmission prior to ending the unicast transmissions(block 3410), publishing availability of the content to mobile entities(block 3412), and enforcing ending unicast transmissions (block 3413).

With reference to FIG. 34C, there are shown further optional operationsor aspects of the method 3400. If the method 3400 includes at least oneblock of FIG. 34C, then the method 3400 may terminate after the at leastone block, without including any subsequent downstream block(s). It isfurther noted that numbers of the blocks do not imply a particular orderin which the blocks may be performed according to the method 3400. Forexample, the method 3400 may further include providing the content viathe multicast transmission subsequent to ending the unicasttransmissions (block 3414), receiving an indication for transmission toa mobile entity to signal to the mobile entity that content delivery isswitching from the unicast transmission mode to the broadcasttransmission mode (block 3416), sending a signaling message to a mobileentity, wherein the signaling message indicates that the contentdelivery is switching from the unicast transmission mode to themulticast transmission mode (block 3418). For example, the signalingmessage may include PCO or a socket configuration. The method 3400 mayfurther include receiving a message from a mobile entity to releaseresources associated with the unicast transmission mode (block 3420),receiving capability reports from mobile entities via PCO (block 3421),and receiving an indication of a start of the multicast transmissionmode (block 3422).

With reference to FIG. 34D, there are shown further optional operationsor aspects of the method 3400. If the method 3400 includes at least oneblock of FIG. 34D, then the method 3400 may terminate after the at leastone block, without including any subsequent downstream block(s). It isfurther noted that numbers of the blocks do not imply a particular orderin which the blocks may be performed according to the method 3400. Forexample, the method 3400 may further include establishing one or moremulticast areas for delivery of the content, in advance of providing thecontent via the unicast transmissions (block 3424), and sending amessage to initiate the multicast transmission from a dynamic adaptivestreaming over HTTP (DASH) proxy at a BM-SC (block 3426).

With reference to FIG. 34E, there are shown further optional operationsor aspects of the method 3400. If the method 3400 includes at least oneblock of FIG. 34E, then the method 3400 may terminate after the at leastone block, without including any subsequent downstream block(s). It isfurther noted that numbers of the blocks do not imply a particular orderin which the blocks may be performed according to the method 3400. Forexample, the method 3400 may further include receiving anotherindication to enable detection associated with content for the unicasttransmissions subsequent to sending the message for initiating themulticast transmission (block 3434), sending a notification message froma BM-SC to a P-GW configured as an IP anchor to indicate the multicasttransmission has started (block 3436), sending an eMBMS session setupmessage for the multicast session to a RAN for establishment of eMBMStransmission (block 3438), and sending a redirect message including aunicast to broadcast transition indication to a mobile entity inresponse to receiving a request for delivery of content via unicastdelivery from the mobile entity (block 3440).

In accordance with one or more aspects of the embodiments describedherein, with reference to FIG. 35, there is shown a methodology 3500,operable by an apparatus, such as for example, the UE. The method is notlimited to performance by the UE, and may be performed by any mobileentity or combination of entities for which the defined operations arepossible and/or permitted by applicable standards. The method 3500 mayinclude, at 3502, receiving an indication that content being deliveredvia unicast transmission or multicast transmission is being transitionedto delivery via unicast transmission or multicast transmission,respectively, in response to a trigger. The method 3500 may furtherinclude, at 3504, switching to receiving the content via the unicasttransmission or multicast transmission, respectively.

FIG. 36A shows an embodiment of an apparatus for implementing ademand-based multicast service in a wireless communication system, inaccordance with the methodology of FIGS. 34A-E. With reference to FIG.36A, there is provided an exemplary apparatus 3600 that may beconfigured as a P-GW or BM-SC component, or as a processor or similardevice/component for use within one of the devices. The apparatus 3600may include functional blocks that can represent functions implementedby a processor, software, hardware, or combination thereof (e.g.,firmware). For example, apparatus 3600 may include a component or module3602 for determining whether an aggregate demand for a content providedvia dedicated unicast transmissions exceeds a threshold. The apparatus3600 may also include a component or module 3604 for switchingtransmission of the content from the dedicated unicast transmissions toa multicast transmission upon a determination that the aggregate demandexceeds the threshold.

In related aspects, the apparatus 3600 may optionally include aprocessor component 3610 having at least one processor, in the case ofthe apparatus 3600 configured as a P-GW or BM-SC, rather than as aprocessor. The processor 3610, in such case, may be in operativecommunication with the components 3602-3604 via a bus 3612 or similarcommunication coupling. The processor 3610 may effect initiation andscheduling of the processes or functions performed by electricalcomponents 3602-3604.

In further related aspects, the apparatus 3600 may include a signalingcomponent 3614. The apparatus 3600 may optionally include a componentfor storing information, such as, for example, a memory device/component3616. The computer readable medium or the memory component 3616 may beoperatively coupled to the other components of the apparatus 3600 viathe bus 3612 or the like. The memory component 3616 may be adapted tostore computer readable instructions and data for effecting theprocesses and behavior of the components 3602-3604, and subcomponentsthereof, or the processor 3610, or the methods disclosed herein. Thememory component 3616 may retain instructions for executing functionsassociated with the components 3602-3604. While shown as being externalto the memory component 3616, it is to be understood that the components3602-3604 can exist within the memory component 3616. It is furthernoted that the components in FIG. 36A may comprise processors,electronic devices, hardware devices, electronic sub-components, logicalcircuits, memories, software codes, firmware codes, etc., or anycombination thereof.

With reference to FIG. 36B, there are shown further optional componentsor modules of the apparatus 3600. For example, the apparatus 3600 mayfurther include a component or module 3620 for determining a count ofmobile entities in an area of the WCS. For example, the apparatus 3600may further include a component or module 3622 for receiving locationinformation of the mobile entities. The apparatus 3600 may furtherinclude a component or module 3624 for providing the content viamulticast transmission prior to ending the unicast transmissions. Theapparatus 3600 may further include a component or module 3626 forpublishing availability of the content to mobile entities. The apparatus3600 may further include a component or module 3627 for enforcing endingunicast transmissions.

With reference to FIG. 36C, there are shown further optional componentsor modules of the apparatus 3600. For example, the apparatus 3600 mayfurther include a component or module 3628 for providing the content viathe multicast transmission subsequent to ending the unicasttransmissions. For example, the apparatus 3600 may further include acomponent or module 3630 for receiving an indication for transmission toa mobile entity to signal to the mobile entity that content delivery isswitching from the unicast transmissions to the broadcast transmission.The apparatus 3600 may further include a component or module 3632 forsending a signaling message to a mobile entity, wherein the signalingmessage indicates that the content delivery is switching from theunicast transmission to the multicast transmission. The apparatus 3600may further include a component or module 3634 for receiving a messagefrom a mobile entity to release resources associated with the unicasttransmission. The apparatus 3600 may further include a component ormodule 3635 for receiving capability reports from mobile entities viaPCO. The apparatus 3600 may further include a component or module 3636for receiving an indication of a start of the multicast transmission.

With reference to FIG. 36D, there are shown further optional componentsor modules of the apparatus 3600. For example, the apparatus 3600 mayfurther include a component or module 3638 for establishing one or moremulticast areas for delivery of the content, in advance of providing thecontent via the unicast transmissions. For example, the apparatus 3600may further include a component or module 3640 for sending a message toinitiate the multicast transmission from a dynamic adaptive streamingover HTTP (DASH) proxy at a BM-SC.

With reference to FIG. 36E, there are shown further optional componentsor modules of the apparatus 3600. For example, the apparatus 3600 mayfurther include a component or module 3648 for receiving anotherindication to enable detection associated with content for the unicasttransmissions subsequent to sending the message for initiating themulticast transmission. For example, the apparatus 3600 may furtherinclude a component or module 3650 for sending a notification messagefrom a BM-SC to a P-GW configured as an IP anchor to indicate themulticast transmission has started. The apparatus 3600 may furtherinclude a component or module 3652 for sending an eMBMS session setupmessage for the multicast session to a RAN for establishment of an eMBMStransmission. The apparatus 3600 may further include a component ormodule 3654 for sending a redirect message including a unicast tobroadcast transition indication to a mobile entity in response toreceiving a request for delivery of content via unicast delivery fromthe mobile entity.

FIG. 37 shows an embodiment of an apparatus for implementing ademand-based multicast service in a wireless communication system, inaccordance with the methodology of FIG. 35. With reference to FIG. 37,there is provided an exemplary apparatus 3700 that may be configured asa UE, or as a processor or similar device/component for use within thedevice. The apparatus 3700 may include functional blocks that canrepresent functions implemented by a processor, software, hardware, orcombination thereof (e.g., firmware). For example, apparatus 3700 mayinclude a component or module 3702 for receiving an indication thatcontent being delivered via unicast transmission or multicasttransmission is being transitioned to delivery via multicasttransmission or unicast transmission, respectively, in response to atrigger. The apparatus 3700 may also include a component or module 3704for switching to receiving the content via multicast transmission orunicast transmission, respectively.

In accordance with one or more aspects of the embodiments describedherein, with reference to FIG. 38, there is shown a methodology 3800,operable by an apparatus, such as for example, a P-GW or a BM-SCincluding a HARD module. The method is not limited to performance by theP-GW or BM-SC and/or HARD module, and may be performed by any networkentity or combination of entities for which the defined operations arepossible and/or permitted by applicable standards. The method 3800 mayinclude, at 3802, determining whether an aggregate demand for contentassociated with a multicast transmission falls below a threshold. Themethod 3800 may further include, at 3804, sending in a broadcast messagean indication that the content is being switched from broadcast deliveryto unicast delivery upon a determination that the aggregate demand fallsbelow the threshold.

FIG. 39 shows another embodiment of an apparatus for implementing ademand-based multicast service in a wireless communication system, inaccordance with the methodology of FIG. 38. With reference to FIG. 39,there is provided an exemplary apparatus 3900 that may be configured asa P-GW or BM-SC component, or as a processor or similar device/componentfor use within one of the devices. The apparatus 3900 may includefunctional blocks that can represent functions implemented by aprocessor, software, hardware, or combination thereof (e.g., firmware).For example, apparatus 3900 may include a component or module 3902 fordetermining whether an aggregate demand for content associated with amulticast transmission falls below a threshold. The apparatus 3900 mayalso include a component or module 3904 for sending in a broadcastmessage an indication that the content is being switched from broadcastdelivery to unicast delivery upon a determination that the aggregatedemand falls below the threshold.

In related aspects, the apparatus 3900 may optionally include aprocessor component 3910 having at least one processor, in the case ofthe apparatus 3900 configured as a P-GW or BM-SC, rather than as aprocessor. The processor 3910, in such case, may be in operativecommunication with the components 3902-3904 via a bus 3912 or similarcommunication coupling. The processor 3910 may effect initiation andscheduling of the processes or functions performed by electricalcomponents 3902-3904.

In further related aspects, the apparatus 3900 may include a signalingcomponent 3914. The apparatus 3900 may optionally include a componentfor storing information, such as, for example, a memory device/component3916. The computer readable medium or the memory component 3916 may beoperatively coupled to the other components of the apparatus 3900 viathe bus 3912 or the like. The memory component 3916 may be adapted tostore computer readable instructions and data for effecting theprocesses and behavior of the components 3902-3904, and subcomponentsthereof, or the processor 3910, or the methods disclosed herein. Thememory component 3916 may retain instructions for executing functionsassociated with the components 3902-3904. While shown as being externalto the memory component 3916, it is to be understood that the components3902-3904 can exist within the memory component 3916. It is furthernoted that the components in FIG. 39 may comprise processors, electronicdevices, hardware devices, electronic sub-components, logical circuits,memories, software codes, firmware codes, etc., or any combinationthereof.

In other embodiments, a MBSFN areaID may also be reported as locationinformation. A location (CGI/MBSFN areaID) may be included only in anMPD fetch. The UE 602 may create a unique content ID for each MPD. TheUE 602 reports the same content ID for every segment fetched from aparticular MPD so the HARD module may determine the MPD from the contentID. In this case, the HARD module may avoid inspecting or parsing theMPD to determine which segment fetch corresponds to which content MPDbecause the HARD module knows the content MPD from the content ID. TheMSK may be included in the redirection signaling message to speed uptransition from UC reception of a content to BC reception of thecontent. When the UE 602 transitions to receiving content throughdelivery via broadcast transmissions, the UE 602 may need to obtain theMSK. When the MSK is included in the redirection signaling message,fewer steps are needed, because the UE 602 may not need to separatelyrequest the MSK and receive the MSK in a separate message. DifferentMPDs may be used to describe UC content and BC content. For example, oneMPD may describe the content delivered via unicast transmission, andanother MPD may describe the content delivered via broadcasttransmission. If different MPDs are used to describe the UC content andthe BC content, the UE 602 may not be aware of the mapping between thetwo MPDs. An indication may be needed for the UE 602 to determine themapping between the UC MPD and BC MPD so that the UE 602 can switchbetween UC reception of a content and BC reception of the content. Inone aspect, the mapping information may be included in the UC MPD, suchas a BC MPD URL reference included in the UC MPD. In another aspect, aservice announcement may provide the mapping information between the UCMPD and BC MPD.

FIG. 40 illustrates a relational mapping for data elements of a userservice bundle, for example, as used in the call flow of FIG. 30. Theunicast and broadcast transmissions may or may not use a common MPD.FIG. 40 illustrates relationships between data elements. Each dataelement may be a data structure. When a first data element includes asecond data element, the two data elements may be included in the samedata structure, as in-line elements. When a first data elementreferences a second data element, a link or reference pointer to thesecond data element may be included in the data structure of the firstdata element. The data elements may be related in a one-to-onerelationship, one-to-many relationship, or many-to-many relationship.

A user service bundle description 4002 is illustrated including userservice descriptions 4006, and optionally including a reference to aforward error correction (FEC) repair stream description 4004. The userservice description 4006 optionally includes amediaPresentationDescription 4016 and includes delivery methods 4008.The delivery method 4008 includes a reference to a session description4012, and optionally includes references to an associated deliveryprocedure description 4010 and a security description 4014. The sessiondescription 4012 may be related to the associated delivery proceduredescription 4010 and security description 4014. ThemediaPresentationDescription 4016 includes a reference to a mediapresentation description MPD 4018. The MPD 4018 may include a UC MPD URL4020 and references to initialization segment descriptions 4022.

In accordance with one or more aspects of the embodiments describedherein, with reference to FIG. 41A, there is shown a methodology 4100,operable by an apparatus, such as for example, a BM-SC or a BM-SCincluding an S-HARD module. The method is not limited to performance bythe BM-SC or BM-SC and/or S-HARD module, and may be performed by anynetwork entity or combination of entities for which the definedoperations are possible and/or permitted by applicable standards. Themethod 4100 may include, at 4102, receiving at least one notification ofa unicast transmission of a content, the unicast transmission being sentfrom another network entity. The method 4100 may further include, at4104, determining, based on the at least one notification, whether anaggregate demand for the content exceeds a threshold. The method 4100may further include, at 4106, switching transmission of the content fromthe unicast transmission to a multicast transmission upon adetermination that the aggregate demand exceeds the threshold.

With reference to FIG. 41B, there are shown further optional operationsor aspects of the method 4100. If the method 4100 includes at least oneblock of FIG. 41B, then the method 4100 may terminate after the at leastone block, without including any subsequent downstream block(s). It isfurther noted that numbers of the blocks do not imply a particular orderin which the blocks may be performed according to the method 4100. Forexample, the method 4100 may further include receiving the at least onenotification at a network entity outside of a transmission path of theunicast transmission (block 4108), transmitting a network destinationfor a mobile entity to transmit the at least one notification (block4110), transmitting a redirect message to a mobile entity indicatingthat content delivery is switching from the unicast transmission tomulticast transmission (block 4112), and determining a count of mobileentities in a defined area of the WCS, wherein the determining theaggregate demand is based on the determined count (block 4114).

In accordance with one or more aspects of the embodiments describedherein, with reference to FIG. 42, there is shown a methodology 4200,operable by an apparatus, such as for example, the UE. The method is notlimited to performance by the UE, and may be performed by any mobileentity or combination of entities for which the defined operations arepossible and/or permitted by applicable standards. The method 4200 mayinclude, at 4202, determining a location for reporting reception of aunicast transmission. The method 4200 may further include, at 4204,transmitting an indication of the unicast transmission to the determinedlocation different from a first network entity transmitting the unicasttransmission. The method 4200 may further include, at 4206, receiving aredirect message indicating that content being delivered via the unicasttransmission is being transitioned to delivery via multicasttransmission.

FIG. 43A shows an embodiment of an apparatus for implementing ademand-based multicast service in a wireless communication system, inaccordance with the methodologies of FIGS. 41A-B. With reference to FIG.43A, there is provided an exemplary apparatus 4300 that may beconfigured as a BM-SC and/or S-HARD module, or as a processor or similardevice/component for use within the device. The apparatus 4300 mayinclude functional blocks that can represent functions implemented by aprocessor, software, hardware, or combination thereof (e.g., firmware).The functional blocks may be implemented by the processor 4310 and/ornetwork interface 4314. The network interface 4314 may be a transmitter,receiver, or transceiver. The functional blocks may be implemented bythe processor 4310 and/or network interface 4314 coupled to the memorycomponent 4316. For example, apparatus 4300 may include a component ormodule 4302 for receiving at least one notification of a unicasttransmission of a content, the unicast transmission being sent fromanother network entity. The component or module 4302 may be performed bythe processor 4310 and/or network interface 4314. The apparatus 4300 mayalso include a component or module 4304 for determining, based on the atleast one notification, whether an aggregate demand for the contentexceeds a threshold. The apparatus 4300 may also include a component ormodule 4306 for switching transmission of the content from the unicasttransmission to a multicast transmission upon a determination that theaggregate demand exceeds the threshold.

In related aspects, the apparatus 4300 may optionally include aprocessor component 4310 having at least one processor, in the case ofthe apparatus 4300 configured as a BM-SC, rather than as a processor.The processor 4310, in such case, may be in operative communication withthe components 4302-4306 via a bus 4312 or similar communicationcoupling. The processor 4310 may effect initiation and scheduling of theprocesses or functions performed by electrical components 4302-4306.

In further related aspects, the apparatus 4300 may include a signalingcomponent 4314. The apparatus 4300 may optionally include a componentfor storing information, such as, for example, a memory device/component4316. The computer readable medium or the memory component 4316 may beoperatively coupled to the other components of the apparatus 4300 viathe bus 4312 or the like. The memory component 4316 may be adapted tostore computer readable instructions and data for effecting theprocesses and behavior of the components 4302-4306, and subcomponentsthereof, or the processor 4310, or the methods disclosed herein. Thememory component 4316 may retain instructions for executing functionsassociated with the components 4302-4306. While shown as being externalto the memory component 4316, it is to be understood that the components4302-4306 can exist within the memory component 4316. It is furthernoted that the components in FIG. 43A may comprise processors,electronic devices, hardware devices, electronic sub-components, logicalcircuits, memories, software codes, firmware codes, etc., or anycombination thereof.

With reference to FIG. 43B, there are shown further optional componentsor modules of the apparatus 4300. For example, the apparatus 4300 mayfurther include a component or module 4320 for receiving the at leastone notification at a network entity outside of a transmission path ofthe unicast transmission. For example, the apparatus 4300 may furtherinclude a component or module 4322 for transmitting a networkdestination for a mobile entity to transmit the at least onenotification. The component or module 4322 may be performed by theprocessor 4310 and/or network interface 4314. The apparatus 4300 mayfurther include a component or module 4324 for transmitting a redirectmessage to a mobile entity indicating that content delivery is switchingfrom the unicast transmission to multicast transmission. The apparatus4300 may further include a component or module 4326 for determining acount of mobile entities in an area of the WCS, wherein the determiningthe aggregate demand is based on the determined count.

FIG. 44 shows an embodiment of an apparatus for implementing ademand-based multicast service in a wireless communication system, inaccordance with the methodology of FIG. 42. With reference to FIG. 44,there is provided an exemplary apparatus 4400 that may be configured asa UE, or as a processor or similar device/component for use within thedevice. The apparatus 4400 may include functional blocks that canrepresent functions implemented by a processor, software, hardware, orcombination thereof (e.g., firmware). The functional blocks may beimplemented by the processor 4410 and/or network interface 4414. Thenetwork interface 4414 may be a transmitter, receiver, or transceiver.The functional blocks may be implemented by the processor 4410 and/ornetwork interface 4414 coupled to the memory 4416. For example,apparatus 4400 may include a component or module 4402 for determining alocation for reporting reception of a unicast transmission. Theapparatus 4400 may also include a component or module 4404 fortransmitting an indication of the unicast transmission to the determinedlocation different from a first network entity transmitting the unicasttransmission. The component or module 4404 may be performed by theprocessor 4410 and/or network interface 4414. The apparatus 4400 mayalso include a component or module 4406 for receiving a redirect messageindicating that content being delivered via the unicast transmission isbeing transitioned to delivery via multicast transmission. The componentor module 4406 may be performed by the processor 4410 and/or networkinterface 4414.

In accordance with one or more aspects of the embodiments describedherein, with reference to FIG. 45, there is shown a methodology 4500,operable by an apparatus, such as for example, a P-GW or a BM-SCincluding a HARD module. The method is not limited to performance by theP-GW or BM-SC and/or HARD module, and may be performed by any networkentity or combination of entities for which the defined operations arepossible and/or permitted by applicable standards. The method 4500 mayinclude, at 4502, determining whether an aggregate demand for a contentprovided via dedicated unicast transmissions exceeds a threshold. Themethod 4500 may further include, at 4504, switching transmission of thecontent from the dedicated unicast transmissions on one frequency to amulticast transmission on a second or more frequencies in response todetermining that the aggregate demand exceeds the threshold. Forexample, the one frequency and second frequency may be the same ordifferent frequencies.

In accordance with one or more aspects of the embodiments describedherein, with reference to FIG. 46, there is shown a methodology 4600,operable by an apparatus, such as for example, a P-GW or a BM-SCincluding a HARD module. The method is not limited to performance by theP-GW or BM-SC and/or HARD module, and may be performed by any networkentity or combination of entities for which the defined operations arepossible and/or permitted by applicable standards. The method 4600 mayinclude, at 4602, receiving a content via multicast transmission. Themethod 4600 may further include, at 4604, determining whethertransmission of the content received via the multicast transmission isabout to end or is no longer available on one or more frequencies. Themethod 4600 may further include, at 4606, switching receiving of thecontent via the multicast transmission to dedicated unicasttransmissions.

In accordance with one or more aspects of the embodiments describedherein, with reference to FIG. 47, there is shown a methodology 4700,operable by an apparatus, such as for example, the UE. The method is notlimited to performance by the UE, and may be performed by any mobileentity or combination of entities for which the defined operations arepossible and/or permitted by applicable standards. The method 4700 mayinclude, at 4702, receiving a content via dedicated unicasttransmission. The method 4700 may further include, at 4704, determiningwhether transmission of the content received via the dedicated unicasttransmission is about to end or is no longer available on a firstfrequency. The method 4700 may further include, at 4706, switchingreceiving of the content via the dedicated unicast transmission tomulticast transmission.

In accordance with one or more aspects of the embodiments describedherein, with reference to FIG. 48, there is shown a methodology 4800,operable by an apparatus, such as for example, a P-GW or a BM-SCincluding a HARD module. The method is not limited to performance by theP-GW or BM-SC and/or HARD module, and may be performed by any networkentity or combination of entities for which the defined operations arepossible and/or permitted by applicable standards. The method 4800 mayinclude, at 4802, determining whether an aggregate demand for a contentprovided via dedicated unicast transmissions exceeds a threshold basedon indications received from mobile entities. The method 4800 mayfurther include, at 4804, switching transmission of the content from thededicated unicast transmissions to a multicast transmission in responseto determining that the aggregate demand exceeds the threshold.

In accordance with one or more aspects of the embodiments describedherein, with reference to FIG. 49, there is shown a methodology 4900,operable by an apparatus, such as for example, a P-GW or a BM-SCincluding a HARD module. The method is not limited to performance by theP-GW or BM-SC and/or HARD module, and may be performed by any networkentity or combination of entities for which the defined operations arepossible and/or permitted by applicable standards. The method 4900 mayinclude, at 4902, determining whether a content can be delivered viaunicast transmission and multicast transmission. The method 4900 mayfurther include, at 4904, provisioning the unicast transmission andmulticast transmission in response to determining the content can bedelivered via unicast transmission, multicast transmission, or both. Themethod 4900 may further include, at 4906, switching between the unicasttransmission and the multicast transmission.

FIG. 50 shows an embodiment of an apparatus for implementing ademand-based multicast service in a wireless communication system, inaccordance with the methodology of FIG. 45. With reference to FIG. 50,there is provided an exemplary apparatus 5000 that may be configured asa P-GW or BM-SC component, or as a processor or similar device/componentfor use within one of the devices. The apparatus 5000 may includefunctional blocks that can represent functions implemented by aprocessor, software, hardware, or combination thereof (e.g., firmware).For example, apparatus 5000 may include a component or module 5020 fordetermining whether an aggregate demand for a content provided viadedicated unicast transmissions exceeds a threshold. The apparatus 5000may also include a component or module 5022 for switching transmissionof the content from the dedicated unicast transmissions on one frequencyto a multicast transmission on a second or more frequencies in responseto determining that the aggregate demand exceeds the threshold.

In related aspects, the apparatus 5000 may optionally include aprocessor component 5010 having at least one processor, in the case ofthe apparatus 5000 configured as a P-GW or BM-SC, rather than as aprocessor. The processor 5010, in such case, may be in operativecommunication with the components 5020-5022 via a bus 5012 or similarcommunication coupling. The processor 5010 may effect initiation andscheduling of the processes or functions performed by electricalcomponents 5020-5022.

In further related aspects, the apparatus 5000 may include a signalingcomponent 5014. The apparatus 5000 may optionally include a componentfor storing information, such as, for example, a memory device/component5016. The computer readable medium or the memory component 5016 may beoperatively coupled to the other components of the apparatus 5000 viathe bus 5012 or the like. The memory component 5016 may be adapted tostore computer readable instructions and data for effecting theprocesses and behavior of the components 5020-5022, and subcomponentsthereof, or the processor 5010, or the methods disclosed herein. Thememory component 5016 may retain instructions for executing functionsassociated with the components 5020-5022. While shown as being externalto the memory component 5016, it is to be understood that the components5020-5022 can exist within the memory component 5016. It is furthernoted that the components in FIG. 50 may comprise processors, electronicdevices, hardware devices, electronic sub-components, logical circuits,memories, software codes, firmware codes, etc., or any combinationthereof.

FIG. 51 shows an embodiment of an apparatus for implementing ademand-based multicast service in a wireless communication system, inaccordance with the methodology of FIG. 46. With reference to FIG. 51,there is provided an exemplary apparatus 5100 that may be configured asa UE, or as a processor or similar device/component for use within thedevice. The apparatus 5100 may include functional blocks that canrepresent functions implemented by a processor, software, hardware, orcombination thereof (e.g., firmware). For example, apparatus 5100 mayinclude a component or module 5120 for receiving a content via multicasttransmission. The apparatus 5100 may also include a component or module5122 for determining whether transmission of the content received viathe multicast transmission is about to end or is no longer available onone or more frequencies. The apparatus 5100 may also include a componentor module 5124 for switching receiving of the content via the multicasttransmission to dedicated unicast transmissions.

In related aspects, the apparatus 5100 may optionally include aprocessor component 5110 having at least one processor, in the case ofthe apparatus 5100 configured as a P-GW or BM-SC, rather than as aprocessor. The processor 5110, in such case, may be in operativecommunication with the components 5120-5124 via a bus 5112 or similarcommunication coupling. The processor 5110 may effect initiation andscheduling of the processes or functions performed by electricalcomponents 5120-5124.

In further related aspects, the apparatus 5100 may include a signalingcomponent 5114. The apparatus 5100 may optionally include a componentfor storing information, such as, for example, a memory device/component5116. The computer readable medium or the memory component 5116 may beoperatively coupled to the other components of the apparatus 5100 viathe bus 5112 or the like. The memory component 5116 may be adapted tostore computer readable instructions and data for effecting theprocesses and behavior of the components 5120-5124, and subcomponentsthereof, or the processor 5110, or the methods disclosed herein. Thememory component 5116 may retain instructions for executing functionsassociated with the components 5120-5124. While shown as being externalto the memory component 5116, it is to be understood that the components5120-5124 can exist within the memory component 5116. It is furthernoted that the components in FIG. 51 may comprise processors, electronicdevices, hardware devices, electronic sub-components, logical circuits,memories, software codes, firmware codes, etc., or any combinationthereof.

FIG. 52 shows an embodiment of an apparatus for implementing ademand-based multicast service in a wireless communication system, inaccordance with the methodology of FIG. 47. With reference to FIG. 52,there is provided an exemplary apparatus 5200 that may be configured asa UE, or as a processor or similar device/component for use within theUE. The apparatus 5200 may include functional blocks that can representfunctions implemented by a processor, software, hardware, or combinationthereof (e.g., firmware). For example, apparatus 5200 may include acomponent or module 5220 for receiving a content via dedicated unicasttransmission. The apparatus 5200 may also include a component or module5222 for determining whether transmission of the content received viathe dedicated unicast transmission is about to end or is no longeravailable on a first frequency. The apparatus 5200 may also include acomponent or module 5224 for switching receiving of the content via thededicated unicast transmission to multicast transmission.

In related aspects, the apparatus 5200 may optionally include aprocessor component 5210 having at least one processor, in the case ofthe apparatus 5200 configured as a UE, rather than as a processor. Theprocessor 5210, in such case, may be in operative communication with thecomponents 5220-5222 via a bus 5212 or similar communication coupling.The processor 5210 may effect initiation and scheduling of the processesor functions performed by electrical components 5220-5224.

In further related aspects, the apparatus 5200 may include a signalingcomponent 5214. The apparatus 5200 may optionally include a componentfor storing information, such as, for example, a memory device/component5216. The computer readable medium or the memory component 5216 may beoperatively coupled to the other components of the apparatus 5200 viathe bus 5212 or the like. The memory component 5216 may be adapted tostore computer readable instructions and data for effecting theprocesses and behavior of the components 5220-5224, and subcomponentsthereof, or the processor 5210, or the methods disclosed herein. Thememory component 5216 may retain instructions for executing functionsassociated with the components 5220-5224. While shown as being externalto the memory component 5216, it is to be understood that the components5220-5224 can exist within the memory component 5216. It is furthernoted that the components in FIG. 52 may comprise processors, electronicdevices, hardware devices, electronic sub-components, logical circuits,memories, software codes, firmware codes, etc., or any combinationthereof.

FIG. 53 shows an embodiment of an apparatus for implementing ademand-based multicast service in a wireless communication system, inaccordance with the methodology of FIG. 48. With reference to FIG. 53,there is provided an exemplary apparatus 5300 that may be configured asa P-GW or BM-SC component, or as a processor or similar device/componentfor use within one of the devices. The apparatus 5300 may includefunctional blocks that can represent functions implemented by aprocessor, software, hardware, or combination thereof (e.g., firmware).For example, apparatus 5300 may include a component or module 5320 fordetermining whether an aggregate demand for a content provided viadedicated unicast transmissions exceeds a threshold based on indicationsreceived from mobile entities. The apparatus 5300 may also include acomponent or module 5322 for switching transmission of the content fromthe dedicated unicast transmissions to a multicast transmission inresponse to determining that the aggregate demand exceeds the threshold.

In related aspects, the apparatus 5300 may optionally include aprocessor component 5310 having at least one processor, in the case ofthe apparatus 5300 configured as a P-GW or BM-SC, rather than as aprocessor. The processor 5310, in such case, may be in operativecommunication with the components 5320-5322 via a bus 5312 or similarcommunication coupling. The processor 5310 may effect initiation andscheduling of the processes or functions performed by electricalcomponents 5320-5322.

In further related aspects, the apparatus 5300 may include a signalingcomponent 5314. The apparatus 5300 may optionally include a componentfor storing information, such as, for example, a memory device/component5316. The computer readable medium or the memory component 5316 may beoperatively coupled to the other components of the apparatus 5300 viathe bus 5312 or the like. The memory component 5316 may be adapted tostore computer readable instructions and data for effecting theprocesses and behavior of the components 5320-5322, and subcomponentsthereof, or the processor 5310, or the methods disclosed herein. Thememory component 5316 may retain instructions for executing functionsassociated with the components 5320-5322. While shown as being externalto the memory component 5316, it is to be understood that the components5320-5322 can exist within the memory component 5316. It is furthernoted that the components in FIG. 53 may comprise processors, electronicdevices, hardware devices, electronic sub-components, logical circuits,memories, software codes, firmware codes, etc., or any combinationthereof.

FIG. 54 shows an embodiment of an apparatus for implementing ademand-based multicast service in a wireless communication system, inaccordance with the methodology of FIG. 49. With reference to FIG. 54,there is provided an exemplary apparatus 5400 that may be configured asa P-GW or BM-SC component, or as a processor or similar device/componentfor use within one of the devices. The apparatus 5400 may includefunctional blocks that can represent functions implemented by aprocessor, software, hardware, or combination thereof (e.g., firmware).For example, apparatus 5400 may include a component or module 5420 fordetermining whether a content can be delivered via unicast transmissionand multicast transmission. The apparatus 5400 may also include acomponent or module 5422 for provisioning the unicast transmission andmulticast transmission in response to determining the content can bedelivered via unicast transmission and multicast transmission. Theapparatus 5400 may also include a component or module 5424 for switchingbetween the unicast transmission and the multicast transmission.

In related aspects, the apparatus 5400 may optionally include aprocessor component 5410 having at least one processor, in the case ofthe apparatus 5400 configured as a P-GW or BM-SC, rather than as aprocessor. The processor 5410, in such case, may be in operativecommunication with the components 5420-5422 via a bus 5412 or similarcommunication coupling. The processor 5410 may effect initiation andscheduling of the processes or functions performed by electricalcomponents 5420-5424.

In further related aspects, the apparatus 5400 may include a signalingcomponent 5414. The apparatus 5400 may optionally include a componentfor storing information, such as, for example, a memory device/component5416. The computer readable medium or the memory component 5416 may beoperatively coupled to the other components of the apparatus 5400 viathe bus 5412 or the like. The memory component 5416 may be adapted tostore computer readable instructions and data for effecting theprocesses and behavior of the components 5420-5424, and subcomponentsthereof, or the processor 5410, or the methods disclosed herein. Thememory component 5416 may retain instructions for executing functionsassociated with the components 5420-5424. While shown as being externalto the memory component 5416, it is to be understood that the components5420-5424 can exist within the memory component 5416. It is furthernoted that the components in FIG. 54 may comprise processors, electronicdevices, hardware devices, electronic sub-components, logical circuits,memories, software codes, firmware codes, etc., or any combinationthereof.

Those of skill in the art would understand that information and signalsmay be represented using any of a variety of different technologies andtechniques. For example, data, instructions, commands, information,signals, bits, symbols, and chips that may be referenced throughout theabove description may be represented by voltages, currents,electromagnetic waves, magnetic fields or particles, optical fields orparticles, or any combination thereof.

Those of skill would further appreciate that the various illustrativelogical blocks, modules, circuits, and algorithm steps described inconnection with the disclosure herein may be implemented as electronichardware, computer software, or combinations of both. To clearlyillustrate this interchangeability of hardware and software, variousillustrative components, blocks, modules, circuits, and steps have beendescribed above generally in terms of their functionality. Whether suchfunctionality is implemented as hardware or software depends upon theparticular application and design constraints imposed on the overallsystem. Skilled artisans may implement the described functionality invarying ways for each particular application, but such implementationdecisions should not be interpreted as causing a departure from thescope of the present disclosure.

The various illustrative logical blocks, modules, and circuits describedin connection with the disclosure herein may be implemented or performedwith a general-purpose processor, a digital signal processor (DSP), anapplication specific integrated circuit (ASIC), a field programmablegate array (FPGA) or other programmable logic device, discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described herein. Ageneral-purpose processor may be a microprocessor, but in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

The steps of a method or algorithm described in connection with thedisclosure herein may be embodied directly in hardware, in a softwaremodule executed by a processor, or in a combination of the two. Asoftware module may reside in RAM memory, flash memory, ROM memory,EPROM memory, EEPROM memory, registers, hard disk, a removable disk, aCD-ROM, or any other form of storage medium known in the art. Anexemplary storage medium is coupled to the processor such that theprocessor can read information from, and write information to, thestorage medium. In the alternative, the storage medium may be integralto the processor. The processor and the storage medium may reside in anASIC. The ASIC may reside in a user terminal. In the alternative, theprocessor and the storage medium may reside as discrete components in auser terminal.

In one or more exemplary designs, the functions described may beimplemented in hardware, software, firmware, or any combination thereof.If implemented in software, the functions may be stored on ortransmitted over as one or more instructions or code on acomputer-readable medium. Computer-readable media includes both computerstorage media and communication media including any medium thatfacilitates transfer of a computer program from one place to another. Astorage media may be any available media that can be accessed by ageneral purpose or special purpose computer. By way of example, and notlimitation, computer-readable media can comprise RAM, ROM, EEPROM,CD-ROM or other optical disk storage, magnetic disk storage or othermagnetic storage devices, or any other medium that can be used to storedesired program code means in the form of instructions or datastructures and that can be accessed by a general-purpose orspecial-purpose computer, or a general-purpose or special-purposeprocessor. Also, any connection may be properly termed acomputer-readable medium to the extent involving non-transitory storageof transmitted signals. For example, if the software is transmitted froma website, server, or other remote source using a coaxial cable, fiberoptic cable, twisted pair, digital subscriber line (DSL), or wirelesstechnologies such as infrared, radio, and microwave, then the coaxialcable, fiber optic cable, twisted pair, DSL, or wireless technologiessuch as infrared, radio, and microwave are included in the definition ofmedium, to the extent the signal is retained in the transmission chainon a storage medium or device memory for any non-transitory length oftime. Disk and disc, as used herein, includes compact disc (CD), laserdisc, optical disc, digital versatile disc (DVD), floppy disk andblu-ray disc where disks usually encode data magnetically, while discshold data encoded optically with lasers. Combinations of the aboveshould also be included within the scope of computer-readable media.

The previous description of the disclosure is provided to enable anyperson skilled in the art to make or use the disclosure. Variousmodifications to the disclosure will be readily apparent to thoseskilled in the art, and the generic principles defined herein may beapplied to other variations without departing from the spirit or scopeof the disclosure. Thus, the disclosure is not intended to be limited tothe examples and designs described herein but is to be accorded thewidest scope consistent with the principles and novel features disclosedherein.

What is claimed is:
 1. A method for managing unicast and multicastservices switching in a multi-band/multi-frequency wirelesscommunications system (WCS) capable of both unicast and multicastsignaling, the method comprising: determining whether an aggregatedemand for a content provided via dedicated unicast transmissionsexceeds a threshold; and switching transmission of the content from thededicated unicast transmissions on one frequency to a multicasttransmission on a second or more frequencies in response to determiningthat the aggregate demand exceeds the threshold.
 2. The method of claim1, wherein the one frequency and second or more frequencies are the samefrequency.
 3. The method of claim 1, further comprising sending to amobile entity a redirect message comprising an indication of the secondor more frequencies.
 4. The method of claim 1, further comprisingsending to a mobile entity at least one of a USD or a SIB comprising anindication of the second or more frequencies.
 5. The method of claim 1,further comprising determining the second or more frequencies over whichthe content is sent via the multicast transmission.
 6. An apparatus formanaging unicast and multicast services switching in amulti-band/multi-frequency wireless communications system (WCS) capableof both unicast and multicast signaling, the apparatus comprising: atleast one processor configured to determine whether an aggregate demandfor a content provided via dedicated unicast transmissions exceeds athreshold, and switch transmission of the content from the dedicatedunicast transmissions on one frequency to a multicast transmission on asecond or more frequencies in response to determining that the aggregatedemand exceeds the threshold; and a memory coupled to the at least oneprocessor for storing data.
 7. The apparatus of claim 6, furthercomprising a transceiver configured to send to a mobile entity aredirect message comprising an indication of the second or morefrequencies.
 8. The apparatus of claim 6, wherein the at least oneprocessor configured to is further configured to determine the second ormore frequencies over which the content is sent via the multicasttransmission.
 9. An apparatus for managing unicast and multicastservices switching in a multi-band/multi-frequency wirelesscommunications system (WCS) capable of both unicast and multicastsignaling, the apparatus comprising: means for determining whether anaggregate demand for a content provided via dedicated unicasttransmissions exceeds a threshold; and means for switching transmissionof the content from the dedicated unicast transmissions on one frequencyto a multicast transmission on a second or more frequencies in responseto determining that the aggregate demand exceeds the threshold.
 10. Theapparatus of claim 9, further comprising transceiver means for sendingto a mobile entity a redirect message comprising an indication of thesecond or more frequencies.
 11. The apparatus of claim 9, furthercomprising means for determining the second or more frequencies overwhich the content is sent via the multicast transmission.
 12. A computerprogram product comprising: a computer-readable medium storing code forcausing at least one computer to: determine whether an aggregate demandfor a content provided via dedicated unicast transmissions exceeds athreshold; and switch transmission of the content from the dedicatedunicast transmissions on one frequency to a multicast transmission on asecond or more frequencies in response to determining that the aggregatedemand exceeds the threshold.
 13. The computer program product of claim12, wherein the computer-readable medium stores code for causing the atleast one computer to send to a mobile entity a redirect messagecomprising an indication of the second or more frequencies.
 14. Thecomputer program product of claim 12, wherein the computer-readablemedium stores code for causing the at least one computer to determinethe second or more frequencies over which the content is sent via themulticast transmission.
 15. A method for managing unicast and multicastservices switching in a wireless mobile entity capable of both unicastand multicast signaling, the method comprising: receiving a content viamulticast transmission; determining whether to switch from receiving thecontent via the multicast transmission to receiving the content viadedicated unicast transmission; and switching receiving the content viamulticast transmission to dedicated unicast transmission based inresponse to determining to switch.
 16. The method of claim 15, furthercomprising determining a location of the content delivered via dedicatedunicast transmission, wherein the switching is further based on thedetermined location.
 17. The method of claim 15, further comprisingreceiving an indication the multicast transmission is ending or nolonger available on a frequency, wherein determining whether to switchcomprises determining based on the received indication.
 18. The methodof claim 16, wherein determining the location comprises autonomouslydetermining at least one URL for the content for the dedicated unicasttransmission based on at least one of a user service description (USD),or a prediction by a set of constructions rules.
 19. The method of claim18, wherein the set of construction rules defines a structure forbuilding the at least one URL for the content.
 20. The method of claim18, wherein determining the location further comprises selecting one ofthe at least one URL as the location based on a pre-determining order orpriority.
 21. The method of claim 15, wherein determining whether toswitch is in response to a handover or a cell reselection.
 22. Themethod of claim 15, further comprising determining an end time of themulticast transmission using schedule fragment information, whereindetermining whether to switch is based on the determined end time. 23.An apparatus capable of both unicast and multicast signaling formanaging unicast and multicast services switching, the apparatuscomprising: at least one processor configured to receive a content viamulticast transmission, determine whether transmission of the contentreceived via the multicast transmission is about to end or is no longeravailable on one or more frequencies, and switch receiving of thecontent via the multicast transmission to dedicated unicasttransmissions; and a memory coupled to the at least one processor forstoring data.
 24. The apparatus of claim 23, wherein the switchingcomprises switching in response to a handover or cell reselection. 25.The apparatus of claim 23, wherein the at least one processor is furtherconfigured to receive a redirect message comprising frequencyinformation indicating a target frequency.
 26. The apparatus of claim23, wherein the at least one processor is further configured to switchreceiving of the content via the multicast transmission on a firstfrequency to a multicast transmission on a second frequency.
 27. Theapparatus of claim 23, wherein the at least one processor is furtherconfigured to determine an end time of the multicast transmission usingschedule fragment information.
 28. An apparatus capable of both unicastand multicast signaling for managing unicast and multicast servicesswitching, the apparatus comprising: means for receiving a content viamulticast transmission; means for determining whether transmission ofthe content received via the multicast transmission is about to end oris no longer available on one or more frequencies; and means forswitching receiving of the content via the multicast transmission todedicated unicast transmissions.
 29. The apparatus of claim 28, whereinthe means for switching is further configured for switching in responseto a handover or cell reselection.
 30. The apparatus of claim 28,further comprising means for receiving a redirect message comprisingfrequency information indicating a target frequency.
 31. The apparatusof claim 28, further comprising means for switching receiving of thecontent via the multicast transmission on a first frequency to amulticast transmission on a second frequency.
 32. The apparatus of claim28, wherein the at least one processor is further configured todetermine an end time of the multicast transmission using schedulefragment information.
 33. A computer program product comprising: acomputer-readable medium storing code for causing at least one computerto: receive a content via multicast transmission; determine whethertransmission of the content received via the multicast transmission isabout to end or is no longer available on one or more frequencies; andswitch receiving of the content via the multicast transmission todedicated unicast transmissions.
 34. The computer program product ofclaim 33, wherein to switch comprises to switch in response to ahandover or cell reselection.
 35. The computer program product of claim33, wherein the computer-readable medium stores code for causing the atleast one computer to receive a redirect message comprising frequencyinformation indicating a target frequency.
 36. The computer programproduct of claim 33, wherein the computer-readable medium stores codefor causing the at least one computer to switch receiving of the contentvia the multicast transmission on a first frequency to a multicasttransmission on a second frequency.
 37. The computer program product ofclaim 33, wherein the computer-readable medium stores code for causingthe at least one computer to determine an end time of the multicasttransmission using schedule fragment information.
 38. A method formanaging unicast and multicast services switching in a wireless mobileentity capable of both unicast and multicast signaling, the methodcomprising: receiving a content via dedicated unicast transmission;determining whether to switch from receiving the content via thededicated unicast transmission to receiving the content via multicasttransmission; switching receiving the content via dedicated unicasttransmission to multicast transmission in response to determining toswitch.
 39. The method of claim 38, further comprising determining alocation for the content delivered via multicast transmission, whereinthe switching is further based on the determined location.
 40. Themethod of claim 39, wherein determining the location comprisesautonomously determining at least one URL for the content delivered viathe multicast transmission based on a user service description (USD), areceived broadcast message from a new cell, or a prediction by a set ofconstructions rules.
 41. The method of claim 40, wherein the set ofconstruction rules defines a structure for building the at least one URLfor the content.
 42. The method of claim 41, wherein determining thelocation further comprises selecting one of the at least one URL as thelocation based on a pre-determining order or priority.
 43. The method ofclaim 38, wherein determining whether to switch is in response to ahandover or a cell reselection.
 44. The method of claim 38, furthercomprising determining a frequency on which that the multicasttransmission is sent based on information received from at least one ofa SIB or USD.
 45. An apparatus capable of both unicast and multicastsignaling for managing unicast and multicast services switching, theapparatus comprising: at least one processor configure to receive acontent via dedicated unicast transmission, determine whether to switchfrom receiving the content via the dedicated unicast transmission toreceiving the content via multicast transmission, and switchingreceiving the content via dedicated unicast transmission to multicasttransmission in response to determining to switch; and a memory coupledto the at least one processor for storing data.
 46. An apparatus capableof both unicast and multicast signaling for managing unicast andmulticast services switching, the apparatus comprising: means forreceiving a content via dedicated unicast transmission; means fordetermining whether to switch from receiving the content via thededicated unicast transmission to receiving the content via multicasttransmission; and means for switching receiving the content viadedicated unicast transmission to multicast transmission in response todetermining to switch.
 47. A computer program product comprising: acomputer-readable medium storing code for causing at least one computerto: receive a content via dedicated unicast transmission; determinewhether to switch from receiving the content via the dedicated unicasttransmission to receiving the content via multicast transmission; andswitch receiving the content via dedicated unicast transmission tomulticast transmission in response to determining to switch.
 48. Amethod for managing unicast and multicast services switching in awireless communications system (WCS) capable of both unicast andmulticast signaling, the method comprising: determining whether anaggregate demand for a content provided via dedicated unicasttransmissions exceeds a threshold based on indications received frommobile entities; and switching transmission of the content from thededicated unicast transmissions to a multicast transmission in responseto determining that the aggregate demand exceeds the threshold.
 49. Themethod of claim 48, wherein switching transmission comprises sending tothe mobile entities a signaling message including an MBMS service key.50. The method of claim 48, wherein the determining the aggregate demandis performed at a content provider or a wireless network of the WCS. 51.The method of claim 50, further comprising sending a message to initiatethe multicast transmission to the BM-SC from a PDN-GW, TDF, or astandalone network entity.
 52. The method of claim 48, wherein theindications comprise location information comprising at least one of acell ID or MBSFN area ID.
 53. The method of claim 49, further comprisingreceiving the location information in a hypertext transfer protocol(HTTP) get message.
 54. The method of claim 48, wherein switchingtransmission comprises sending to the mobile entities a signalingmessage in one of an HTTP error message or RTCP message.
 55. The methodof claim 48, wherein determining comprises determining the aggregatedemand based on an MBSFN area or an MBMS service area.
 56. The method ofclaim 48, wherein determining comprises determining based on protocolconfigure options (PCO).
 57. The method of claim 48, further comprisingtransmitting a user service description (USD) to the mobile entitiesthrough unicast transmissions prior to switching transmission of thecontent.
 58. An apparatus for managing unicast and multicast servicesswitching in a wireless communications system (WCS) capable of bothunicast and multicast signaling, the apparatus comprising: at least oneprocessor configured to determine whether an aggregate demand for acontent provided via dedicated unicast transmissions exceeds a thresholdbased on indications received from mobile entities, and switchtransmission of the content from the dedicated unicast transmissions toa multicast transmission in response to determining that the aggregatedemand exceeds the threshold; and a memory coupled to the at least oneprocessor for storing data.
 59. The apparatus of claim 58, wherein theindications comprise location information comprising at least one of acell ID or MBSFN area ID.
 60. The apparatus of claim 59, wherein the atleast one processor is further configured to receive the locationinformation in a hypertext transfer protocol (HTTP) get message.
 61. Theapparatus of claim 58, wherein to switch transmission comprises to sendto the mobile entities a signaling message in one of an HTTP errormessage or RTCP message.
 62. The apparatus of claim 58, wherein todetermine comprises to determine the aggregate demand based on an MBSFNarea or an MBMS service area.
 63. The apparatus of claim 58, wherein todetermine comprises to determine based on protocol configure options(PCO).
 64. The apparatus of claim 58, wherein the at least one processoris further configured to transmit a user service description (USD) tothe mobile entities through unicast prior to switching transmission ofthe content.
 65. An apparatus for managing unicast and multicastservices switching in a wireless communications system (WCS) capable ofboth unicast and multicast signaling, the apparatus comprising: meansfor determining whether an aggregate demand for a content provided viadedicated unicast transmissions exceeds a threshold based on indicationsreceived from mobile entities; and means for switching transmission ofthe content from the dedicated unicast transmissions to a multicasttransmission in response to determining that the aggregate demandexceeds the threshold.
 66. The apparatus of claim 65, wherein theindications comprise location information comprising at least one of acell ID or MBSFN area ID.
 67. The apparatus of claim 66, furthercomprising means for receiving the location information in a hypertexttransfer protocol (HTTP) get message.
 68. The apparatus of claim 65,wherein the means for switching transmission is further configured forsending to the mobile entities a signaling message in one of an HTTPerror message or RTCP message.
 69. The apparatus of claim 65, whereinthe means for determining is further configured for determining theaggregate demand based on an MBSFN area or an MBMS service area.
 70. Theapparatus of claim 65, wherein the means for determining is furtherconfigured for determining based on protocol configure options (PCO).71. The apparatus of claim 65, further comprising means for transmittinga user service description (USD) to the mobile entities through unicastprior to switching transmission of the content.
 72. A computer programproduct comprising: a computer-readable medium storing code for causingat least one computer to: determine whether an aggregate demand for acontent provided via dedicated unicast transmissions exceeds a thresholdbased on indications received from mobile entities; and switchtransmission of the content from the dedicated unicast transmissions toa multicast transmission in response to determining that the aggregatedemand exceeds the threshold.
 73. The computer program product of claim72, wherein the indications comprise location information comprising atleast one of a cell ID or MBSFN area ID.
 74. The computer programproduct of claim 73, wherein the at least one processor is furtherconfigured to receive the location information in a hypertext transferprotocol (HTTP) get message.
 75. The computer program product of claim72, wherein to switch transmission comprises to send to the mobileentities a signaling message in one of an HTTP error message or RTCPmessage.
 76. The computer program product of claim 72, wherein todetermine comprises to determine the aggregate demand based on an MBSFNarea or an MBMS service area.
 77. The computer program product of claim72, wherein to determine comprises to determine based on protocolconfigure options (PCO).
 78. The computer program product of claim 72,wherein the computer-readable medium stores code for causing the atleast one computer to transmit a user service description (USD) to themobile entities through unicast prior to switching transmission of thecontent.
 79. A method for managing demand-based multicast services in awireless communication system (WCS) capable of both unicast andmulticast signaling, the method comprising: determining whether acontent can be delivered via unicast transmission and multicasttransmission; provisioning the unicast transmission and multicasttransmission in response to determining the content can be delivered viaunicast transmission and multicast transmission; and switching betweenthe unicast transmission and the multicast transmission.
 80. The methodof claim 79, wherein the unicast transmission comprises an over-the-top(OTT) service and the multicast transmission comprises an MBMS service.81. The method of claim 79, wherein the unicast transmission comprises aunicast MBMS service and the multicast transmission comprises an MBMSservice.
 82. The method of claim 79, wherein the unicast transmissioncomprises unicast packet switched streaming (PSS) and the multicasttransmission comprises an MBMS service.
 83. An apparatus for managingdemand-based multicast services in a wireless communication system (WCS)capable of both unicast and multicast signaling, the apparatuscomprising: at least one processor configured to (a) determine whether acontent can be delivered via unicast transmission and multicasttransmission, (b) provision the unicast transmission and multicasttransmission in response to determining the content can be delivered viaunicast transmission and multicast transmission, and (c) switch betweenthe unicast transmission and the multicast transmission; and a memorycoupled to the at least one processor for storing data.
 84. Theapparatus of claim 83, wherein the unicast transmission comprises anover-the-top (OTT) service and the multicast transmission comprises anMBMS service.
 85. The apparatus of claim 83, wherein the unicasttransmission comprises a unicast MBMS service and the multicasttransmission comprises an MBMS service.
 86. The apparatus of claim 83,wherein the unicast transmission comprises unicast packet switchedstreaming (PSS) and the multicast transmission comprises an MBMSservice.
 87. An apparatus for managing demand-based multicast servicesin a wireless communication system (WCS) capable of both unicast andmulticast signaling, the apparatus comprising: means for determiningwhether a content can be delivered via unicast transmission andmulticast transmission; means for provisioning the unicast transmissionand multicast transmission in response to determining the content can bedelivered via unicast transmission and multicast transmission; and meansfor switching between the unicast transmission and the multicasttransmission.
 88. The apparatus of claim 87, wherein the unicasttransmission comprises an over-the-top (OTT) service and the multicasttransmission comprises an MBMS service.
 89. The apparatus of claim 87,wherein the unicast transmission comprises a unicast MBMS service andthe multicast transmission comprises an MBMS service.
 90. The apparatusof claim 87, wherein the unicast transmission comprises unicast packetswitched streaming (PSS) and the multicast transmission comprises anMBMS service.
 91. A computer program product comprising: acomputer-readable medium storing code for causing at least one computerto: determine whether a content can be delivered via unicasttransmission and multicast transmission; provision the unicasttransmission and multicast transmission in response to determining thecontent can be delivered via unicast transmission and multicasttransmission; and switch between the unicast transmission and themulticast transmission.
 92. The computer program product of claim 91,wherein the unicast transmission comprises an over-the-top (OTT) serviceand the multicast transmission comprises an MBMS service.
 93. Thecomputer program product of claim 91, wherein the unicast transmissioncomprises a unicast MBMS service and the multicast transmissioncomprises an MBMS service.
 94. The computer program product of claim 91,wherein the unicast transmission comprises unicast packet switchedstreaming (PSS) and the multicast transmission comprises an MBMSservice.